Skip to content

ci(release): use OCTOKITBOT_PAT as GITHUB_TOKEN - #159

Merged
gr2m merged 1 commit into
masterfrom
oscard0m-patch-1
Jul 9, 2022
Merged

gr2m merged 1 commit into
masterfrom
oscard0m-patch-1

Conversation

@oscard0m

@oscard0m oscard0m commented Jul 9, 2022

Copy link
Copy Markdown
Member

Fix #158

@oscard0m
oscard0m requested a review from gr2m July 9, 2022 21:07
@gr2m
gr2m merged commit 92d8e64 into master Jul 9, 2022
@gr2m
gr2m deleted the oscard0m-patch-1 branch July 9, 2022 21:16
@gr2m

gr2m commented Jul 9, 2022

Copy link
Copy Markdown
Contributor

I changed the commit to fix(... to test if the setup works

@gr2m

gr2m commented Jul 9, 2022

Copy link
Copy Markdown
Contributor

hmm that failed 🤔

@oscard0m

oscard0m commented Jul 9, 2022

Copy link
Copy Markdown
Member Author

hmm that failed 🤔

is ${{ secrets.OCTOKITBOT_PAT }} for this repository already?

@gr2m

gr2m commented Jul 9, 2022

Copy link
Copy Markdown
Contributor

Yes OCTOKITBOT_PAT is set for all @octokit repositories

@octokitbot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 2.1.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@gr2m

gr2m commented Jul 9, 2022

Copy link
Copy Markdown
Contributor

okay, we have to pass the PAT to the actions/checkout step as well, this article reminded me of that:
https://www.paulmowat.co.uk/blog/resolve-github-action-gh006-protected-branch-update-failed

      - uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b # tag=v3
        with:
          token: ${{ secrets.OCTOKITBOT_PAT }}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PRs are mergeable with check runs failing and no approvals in this repository

3 participants