Skip to content

Commit

Permalink
chore: migrate from REPO_TOKEN to GITHUB_TOKEN (#157)
Browse files Browse the repository at this point in the history
Switch to using GitHub's built-in GITHUB_TOKEN instead of our custom
REPO_TOKEN in CI workflows.
  • Loading branch information
JoshuaBatty authored Jan 22, 2025
1 parent 8030254 commit 9909e24
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
3 changes: 2 additions & 1 deletion .github/workflows/patch-pr.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ jobs:
# Give the default GITHUB_TOKEN write permission to commit and push the
# added or changed files to the repository.
contents: write
pull-requests: write
steps:
- uses: actions/checkout@v3
with:
Expand Down Expand Up @@ -54,5 +55,5 @@ jobs:
- name: Push changes
uses: ad-m/github-push-action@master
with:
github_token: ${{ secrets.REPO_TOKEN }}
github_token: ${{ secrets.GITHUB_TOKEN }}
branch: ${{ github.head_ref }}
2 changes: 1 addition & 1 deletion .github/workflows/refresh-manifests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ jobs:
- name: Push changes
uses: ad-m/github-push-action@master
with:
github_token: ${{ secrets.REPO_TOKEN }}
github_token: ${{ secrets.GITHUB_TOKEN }}
branch: master

notify-slack-on-failure:
Expand Down

0 comments on commit 9909e24

Please sign in to comment.