Skip to content

Commit

Permalink
Use a custom GitHub token in the backport action
Browse files Browse the repository at this point in the history
Due to a limitation of the GitHub Actions default tokens, Pull Requests
opened with them won't trigger any events. Hence, they won't trigger the
CI builds. Use a custom token to circumvent that and let backport PRs be
built on CI.

Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
(cherry picked from commit 97d26b2)
(cherry picked from commit e019731)
  • Loading branch information
twz123 authored and github-actions[bot] committed Jul 29, 2022
1 parent 8b7201f commit 504bce0
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/backport.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ jobs:
uses: zeebe-io/backport-action@v0.0.8
with:
# Config README: https://github.com/zeebe-io/backport-action#backport-action
github_token: ${{ secrets.GITHUB_TOKEN }}
github_token: ${{ secrets.GH_BACKPORT_TOKEN }}
github_workspace: ${{ github.workspace }}
# should be kept in sync with `uses`
version: v0.0.8
Expand All @@ -48,4 +48,4 @@ jobs:

pull_description: |-
Automated backport to `${target_branch}`, triggered by a label in #${pull_number}.
See ${issue_refs}.
See ${issue_refs}.

0 comments on commit 504bce0

Please sign in to comment.