On this page
GitHub APP Token
This page explains how to use the temporary GitHub App installation token that Pipelines-as-Code generates, so you can interact with the GitHub API from your PipelineRuns. Use this when your pipeline needs to post comments, update statuses, or call other GitHub endpoints.
Accessing the token
Pipelines-as-Code generates a temporary installation token from the GitHub App for each PipelineRun. You can use this token to access the GitHub API. The token value is stored in the temporary git-auth secret that Pipelines-as-Code generates for private repositories, under the key git-provider-token.
sequenceDiagram
%% title: How the GitHub App token reaches a task step
participant GH as GitHub
participant Ctrl as Controller
participant Sec as Git auth secret
participant Step as Task step
GH->>Ctrl: webhook
Ctrl->>GH: ask for an installation token
GH->>Ctrl: token scoped to the repository
Ctrl->>Sec: create pac-gitauth secret with git-provider-token
Ctrl->>Step: PipelineRun with {{ git_auth_secret }}
Sec->>Step: GITHUB_TOKEN
Step->>GH: comment on the pull request
Sec->>Sec: deleted with the PipelineRun
%% play: Token for a PipelineRun
%% GH -> Ctrl : event
%% Ctrl -> GH | The controller asks GitHub for a token of the App installation
%% GH -> Ctrl : token | It is valid for one hour and limited to the repository by default
%% Ctrl -> Sec | The token goes into the git auth secret under git-provider-token
%% Ctrl -> Step | The secret name is passed to the PipelineRun as {{ git_auth_secret }}
%% Sec -> Step : token | A step reads the key from the secret
%% wait 800
%% Step -> GH : API call | and calls the GitHub API with it
%% Sec -> Sec | The secret is owned by the PipelineRun and goes away with itAdding a comment to a pull request
To add a comment to a pull request, use the github-add-comment task from Artifact Hub (a public registry for discovering Tekton tasks and other cloud-native artifacts) with a Pipelines-as-Code annotation:
pipelinesascode.tekton.dev/task: "github-add-comment"Then add the task to your tasks section (or finally tasks) of your PipelineRun:
[...]
tasks:
- name:
taskRef:
name: github-add-comment
params:
- name: REQUEST_URL
value: "{{ repo_url }}/pull/{{ pull_request_number }}"
- name: COMMENT_OR_FILE
value: "Pipelines-as-Code IS GREAT!"
- name: GITHUB_TOKEN_SECRET_NAME
value: "{{ git_auth_secret }}"
- name: GITHUB_TOKEN_SECRET_KEY
value: "git-provider-token"Because this configuration uses dynamic variables, it works for any pull request across any repository without modification.
Setting GITHUB_TOKEN as an environment variable
You can also set the GITHUB_TOKEN environment variable directly on a task step. This approach is useful when you want to call the GitHub API from a custom script rather than a dedicated task:
env:
- name: GITHUB_TOKEN
valueFrom:
secretKeyRef:
name: "{{ git_auth_secret }}"
key: "git-provider-token"- On GitHub Apps, the generated installation token expires after one hour.
- On GitHub Apps, Pipelines-as-Code scopes the token to the repository the event originates from, unless you configure it differently on the cluster.
- To restrict the token to specific extra repositories or understand scoping in detail, see GitHub Token Scoping.