You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?
GitHub Action
Create GitHub App Token
v1.1.0
GitHub Action for creating a GitHub App installation access token.
In order to use this action, you need to:
- Register new GitHub App
- Store the App's ID in your repository environment variables (example:
APP_ID
) - Store the App's private key in your repository secrets (example:
PRIVATE_KEY
)
on: [issues]
jobs:
hello-world:
runs-on: ubuntu-latest
steps:
- uses: actions/create-github-app-token@v1
id: app-token
with:
app_id: ${{ vars.APP_ID }}
private_key: ${{ secrets.PRIVATE_KEY }}
- uses: peter-evans/create-or-update-comment@v3
with:
token: ${{ steps.app-token.outputs.token }}
issue-number: ${{ github.event.issue.number }}
body: "Hello, World!"
on: [pull_request]
jobs:
auto-format:
runs-on: ubuntu-latest
steps:
- uses: actions/create-github-app-token@v1
id: app-token
with:
# required
app_id: ${{ vars.APP_ID }}
private_key: ${{ secrets.PRIVATE_KEY }}
- uses: actions/checkout@v3
with:
token: ${{ steps.app-token.outputs.token }}
ref: ${{ github.head_ref }}
# Make sure the value of GITHUB_TOKEN will not be persisted in repo's config
persist-credentials: false
- uses: creyD/[email protected]
with:
github_token: ${{ steps.app-token.outputs.token }}
Required: GitHub App ID.
Required: GitHub App private key.
GitHub App installation access token.
The action creates an installation access token using the POST /app/installations/{installation_id}/access_tokens
endpoint. By default,
- The token is scoped to the current repository.
- The token inherits all the installation's permissions.
- The token is set as output
token
which can be used in subsequent steps. - The token is revoked in the
post
step of the action, which means it cannot be passed to another job. - The token is masked, it cannot be logged accidentally. That is not a feature by the action, but by the GitHub Actions runner itself, due to the specific format of GitHub tokens.
Note
Installation permissions can differ from the app's permissions they belong to. Installation permissions are set when an app is installed on an account. When the app adds more permissions after the installation, an account administrator will have to approve the new permissions before they are set on the installation.