297 Search results for "secrets"

With push protection, secret scanning blocks contributors from pushing secrets to a repository and generates an alert whenever a contributor bypasses the

provider. This will let you stop storing these credentials as long-lived secrets and provide other security benefits. For more information, see "About

are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to GitHub Actions. If an output

deployments with custom deployment protection rules, or limit access to secrets. For more information about creating environments, see "Managing environments

provider. This will let you stop storing these credentials as long-lived secrets and provide other security benefits. For more information, see "About

GitHub. See "About the CodeQL CLI." Secret scanning - Detect secrets, for example keys and tokens, that have been checked into private repositories

workflows. Storing secrets If your workflows use sensitive data, such as passwords or certificates, you can save these in GitHub as secrets and then use them

limits. Managing development environment secrets for your repository or organization Development environment secrets allow you to store sensitive information

contains GitHub Actions workflows, the option is Allow edits and access to secrets by maintainers. Allowing edits on a fork's branch that contains GitHub Actions

Code scanning results Commit status checks Dependabot alerts Dependabot secrets Discussions at the repository level Edit history of issue comments and pull