Skip to content

Conversation

@currantw
Copy link
Collaborator

Adds a git-secrets-scan workflow that installs and executes git-secrets on pushes to main and release branches. This helps to ensure that passwords, secrets, and other sensitive information does not get committed.

Checklist

Before submitting the PR make sure the following are checked:

  • This Pull Request is related to one issue.
  • Commit message has a detailed description of what changed and why.
  • Tests are added or updated.
  • CHANGELOG.md and documentation files are updated.
  • Destination branch is correct - main or release
  • Create merge commit if merging release branch into main, squash otherwise.

@currantw currantw self-assigned this Nov 18, 2025
@currantw currantw requested a review from affonsov November 18, 2025 20:07
@currantw
Copy link
Collaborator Author

Steps for running locally:

brew install git-secrets
cd <ROOT_DIR>
git secrets --register-aws
git secrets --scan

Signed-off-by: currantw <[email protected]>
Signed-off-by: currantw <[email protected]>
@currantw currantw force-pushed the currantw/git-secrets branch from 9aab2d9 to 92f61c4 Compare November 19, 2025 21:15
Copy link
Collaborator

@yipin-chen yipin-chen left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@affonsov affonsov left a comment

Choose a reason for hiding this comment

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

@currantw currantw merged commit 33c3566 into main Nov 25, 2025
19 checks passed
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.

6 participants