151 Suchergebnisse für "secrets"

see the Supported secrets section below. If you use the REST API for secret scanning, you can use the Secret type to report on secrets from specific issuers

geheimen Schlüssels verschlüsseln. About encrypting secrets Several REST API endpoints let you create secrets on GitHub. To use these endpoints, you must encrypt

you'll need to create a GitHub App and store the app ID and private key as secrets. For more information, see Making authenticated API requests with a GitHub

tokens, and other secrets in your repository. When enabled, secret scanning scans commits in repositories for known types of secrets and alerts repository

/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}

called workflow is automatically granted access to github.token and secrets.GITHUB_TOKEN. For more information about the github context, see Accessing contextual

see Automatic token authentication. For more information about secrets, see Using secrets in GitHub Actions. The following example workflow uses the List

prevents you from accidentally committing secrets to a repository by blocking commits containing supported secrets. GitHub will also block the commit if you