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

an AI-powered expansion of secret scanning that identifies unstructured secrets (passwords) in your source code and then generates an alert. GitHub Advanced

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

information, such as secrets or tokens, from being pushed to your repository in the first place. Unlike secret scanning, which detects secrets after they have

репозитории. Understanding why push protection has blocked your commit Leaked secrets can pose serious security risks to your repository and your supply chain

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

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

protection for users automatically protects you from accidentally committing secrets to public repositories across GitHub. When you try to push a secret to a

security features GitHub has security features that help keep code and secrets secure in repositories and across organizations. Some features are available

io/artifactory/my-gradle-registry username: octocat password: ${{secrets.MY_ARTIFACTORY_PASSWORD}} updates: - package-ecosystem: "gradle" directory: