Skip to content

Conversation

@jamesnrokt
Copy link
Collaborator

Background

  • There have been instances where API keys have been committed to the code base. This PR aims to prevent that with the addition of a Trunk rule

What Has Changed

  • Trunk rule and lint workflow

Screenshots/Video

Tested by adding an API key to a file
Screenshot 2026-01-12 at 1 02 15 PM

Checklist

  • I have performed a self-review of my own code.
  • I have tested this locally.

Additional Notes

  • N/A

Reference Issue (For employees only. Ignore if you are an outside contributor)

  • Closes N/A

@jamesnrokt jamesnrokt requested a review from a team as a code owner January 12, 2026 18:05
Copy link

@nickolas-dimitrakas nickolas-dimitrakas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sonarqubecloud
Copy link

@jamesnrokt jamesnrokt merged commit 3f3c79f into main Jan 12, 2026
15 of 17 checks passed
@jamesnrokt jamesnrokt deleted the feat/add-trunk-api-key-rule branch January 12, 2026 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants