310 Search results for "secrets"
GitHub Actions / Write workflows / Choose what workflows do /
Store information in variables
for sensitive information, such as passwords, use secrets instead. For more information, see Using secrets in GitHub Actions.
Defining environment variables
Code security / Secret scanning / Enable features /
Enabling push protection for your repository
With push protection, secret scanning blocks contributors from pushing secrets to a repository and generates an alert whenever a contributor bypasses the
GitHub Actions / Use cases and examples / Deployment /
Deploying to Amazon Elastic Container Service
provider. This will let you stop storing these credentials as long-lived secrets and provide other security benefits. For more information, see About security
Repositories / Manage repository settings / Enable features /
Managing security and analysis settings for your repository
dependency to a more secure version.
Secret scanning scans your repository for secrets (such as API keys and tokens) and alerts you if a secret is found, so that
Migrations / GitHub Enterprise Importer / Migrate between GitHub products /
About migrations between GitHub products
Code scanning results
Commit status checks
Dependabot alerts
Dependabot secrets
Discussions at the repository level
Edit history of issue comments and pull
GitHub Actions / Write workflows / Choose what workflows do /
Passing information between jobs
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
GitHub Actions / Use cases and examples / Deployment /
Deploying Java to Azure App Service
provider. This will let you stop storing these credentials as long-lived secrets and provide other security benefits. For more information, see About security
GitHub Actions / Use cases and examples / Deployment /
Deploying Node.js to Azure App Service
provider. This will let you stop storing these credentials as long-lived secrets and provide other security benefits. For more information, see About security
Pull requests / Collaborate with pull requests / Working with forks /
Allowing changes to a pull request branch created from a fork
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
GitHub Actions / Write workflows / Choose what workflows do /
Using environments for deployment
deployments with custom deployment protection rules, or limit access to secrets. For more information about creating environments, see Managing environments