Skip to content

Add Guidance on Gitleaks GitHub Action License Requirements#118

Merged
cschilly merged 1 commit intomainfrom
isaac-add-gitleaks-license-guidance
Mar 24, 2026
Merged

Add Guidance on Gitleaks GitHub Action License Requirements#118
cschilly merged 1 commit intomainfrom
isaac-add-gitleaks-license-guidance

Conversation

@IsaacMilarky
Copy link
Copy Markdown
Contributor

Add Guidance on Gitleaks GitHub Action License Requirements

Problem

We do not have resources explaining why larger GitHub organizations are expected to get a license to use the mainline gitleaks GitHub action.

Solution

Write a short guide and link it in the DSAC engineering handbook.

Signed-off-by: Isaac Milarsky <isaac.milarsky@hhs.cms.gov>
@natalialuzuriaga natalialuzuriaga requested a review from a team March 23, 2026 22:13
- Secret Scanning using [gitleaks.yml](https://github.com/DSACMS/repo-scaffolder/blob/main/tier3/%7B%7Bcookiecutter.project_slug%7D%7D/.github/workflows/gitleaks.yml)
- [Github’s CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)

> [!NOTE]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Tagging @DSACMS/eng-handbook-approvers to review this new addition to the DSAC Engineering Handbook!

Copy link
Copy Markdown
Contributor

@natalialuzuriaga natalialuzuriaga left a comment

Choose a reason for hiding this comment

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

LGTM! Good to merge once we get +1 from @DSACMS/eng-handbook-approvers

@natalialuzuriaga natalialuzuriaga requested a review from a team March 23, 2026 22:15
@cschilly cschilly merged commit c37f3a0 into main Mar 24, 2026
5 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.

3 participants