54 検索結果 "secrets"

your secret using LibSodium. For more information, see "Encrypting secrets for the REST API." OAuth app tokens and personal access tokens (classic)

protection for your own personal account, which prevents you from pushing secrets to any public repository on GitHub. For more information, see Push protection

namespace: VAULT-NAMESPACE # HCP Vault and Vault Enterprise only role: ROLE-NAME secrets: SECRET-PATH - name: Use secret from Vault run: | # This step has access

and provisioning profile env: BUILD_CERTIFICATE_BASE64: ${{ secrets.BUILD_CERTIFICATE_BASE64 }} P12_PASSWORD: ${{ secrets.P12_PASSWORD }} BUILD_PROVISION_PROFILE_BASE64:

organization from vulnerabilities in your code, insecure dependencies, leaked secrets, and more. For more information on GitHub Advanced Security, see About GitHub

secret to the cloud provider every time it runs. However, using hardcoded secrets requires you to create credentials in the cloud provider and then duplicate

フォークに GitHub Actions ワークフローが含まれている場合、オプションは [Allow edits and access to secrets by maintainers] になります。 GitHub Actionsワークフローを含むフォークのブランチの編集を許可すると、メンテナにフ

creating a personal access token for the action to use and then storing it in secrets For UI based tasks, include the button or options the users should click

string The leve of permission to grant the access token to manage Dependabot secrets. 次のいずれかにできます: read, write deployments string The level of permission to

フォークに GitHub Actions ワークフローが含まれている場合、オプションは [Allow edits and access to secrets by maintainers] になります。 GitHub Actionsワークフローを含むフォークのブランチの編集を許可すると、メンテナにフ