311 Search results for "secrets"

allow the use of AI to detect secrets that cannot be identified using regular expressions (also known as generic secrets or as non-provider patterns).

About push protection alerts Push protection scans pushes for supported secrets. If push protection detects a supported secret, it will block the push.

from secret scanning Learn how to find, evaluate, and resolve alerts for secrets stored in your repository. About secret scanning alerts Learn about the

/orgs/{org}/actions/secrets GET /orgs/{org}/actions/secrets/public-key GET /orgs/{org}/actions/secrets/{secret_name} PUT /orgs/{org}/actions/secrets/{secret_name}

/orgs/{org}/actions/secrets GET /orgs/{org}/actions/secrets/public-key GET /orgs/{org}/actions/secrets/{secret_name} PUT /orgs/{org}/actions/secrets/{secret_name}

/orgs/{org}/actions/secrets GET /orgs/{org}/actions/secrets/public-key GET /orgs/{org}/actions/secrets/{secret_name} PUT /orgs/{org}/actions/secrets/{secret_name}

secret compromised. GitHub recommends the following actions for compromised secrets: Verify that the secret committed to GitHub is valid. Applies to GitHub

REST API/ Secret scanning/ Secret scanning REST API endpoints for secret scanning Use the REST API to retrieve and update secret alerts from a repository

GITHUB_TOKEN by using the standard syntax for referencing secrets: ${{ secrets.GITHUB_TOKEN }}. Examples of using the GITHUB_TOKEN include passing the

pull requests, discussions, and wikis in those repositories, for leaked secrets that have been accidentally committed, such as tokens or private keys. There