github-release

To prevent accidental secret disclosure during a GitHub release, you can run a gated workflow that scans your repository using gitleaks. This blocks the release pipeline if findings are detected and provides guidance for cleaning history if needed.

The best way to automate version tagging via the GitHub CLI is using a two-phase process that validates your repository hygiene and then creates version tags using git. After safety checks pass, it publishes the GitHub Release using the authenticated gh CLI.

Yes, preparing an open-source GitHub release requires validating the presence of a LICENSE file and checking the README for expected sections. This release hygiene validation ensures your project meets public publishing standards before tagging.

Before creating a GitHub Release, a secrets scan and hygiene check will remove or ignore personal working files. This prevents stray personal artifacts from being published alongside your validated open-source or private project artifacts.

No, you cannot use the gh CLI to publish a release if gitleaks detects sensitive data. The gated workflow blocks the release publication process until the secrets scanning phase passes without any findings.