Skip to content

Conversation

@spacebear21
Copy link
Collaborator

Instead of using the default read-only GITHUB_TOKEN, use the newly created GH_TOKEN_FOR_UPDATES personal access token which has "create PR" permissions on the repo.

Instead of using the default read-only GITHUB_TOKEN, use the newly created GH_TOKEN_FOR_UPDATES [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token) which has "create PR" permissions on the repo.
Copy link
Collaborator

@benalleng benalleng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

uTAck

@benalleng benalleng merged commit c6cb937 into master Jan 19, 2026
26 checks passed
@spacebear21 spacebear21 deleted the spacebear21-patch-3 branch January 19, 2026 18:17
@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 21147606385

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 83.357%

Totals Coverage Status
Change from base Build 21099359114: 0.0%
Covered Lines: 9937
Relevant Lines: 11921

💛 - Coveralls

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.

4 participants