110 Результаты поиска для "secrets"

to provide personal secrets such as API keys to run the application in your template, you can prompt them to provide these secrets. For more information

see Building and testing. Some workflow templates use secrets. For example, ${{ secrets.npm_token }}. If the workflow template uses a secret, store the

compromise the self-hosted runner environment, including gaining access to secrets and the GITHUB_TOKEN which, depending on its settings, can grant write access

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

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

Create, update, and delete GitHub Actions secrets on GitHub.com Create, update, and delete GitHub Actions secrets using the REST API Create and edit releases

private keys for GitHub Apps. For more information about storing secrets, see Using secrets in GitHub Actions. Install the GitHub App on your user account

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

following constructs manually: Mandatory build tools Scripted pipelines Secrets Self-hosted runners Unknown plugins For more information on manual migrations

Certain Travis CI constructs must be migrated manually. These include: Secrets Unknown job properties For more information on manual migrations, see Migrating