Remove GITHUB_TOKEN from readme examples#350
Merged
benschwarz merged 1 commit intocalibreapp:mainfrom Sep 4, 2025
Merged
Conversation
After calibreapp#341 the `GITHUB_TOKEN` input parameter isn't needed unless customizing the token
|
|
kdeldycke
added a commit
to kdeldycke/repomatic
that referenced
this pull request
Aug 30, 2025
Member
|
Thanks @karlhorky 🤙 |
Contributor
Author
|
Glad to help, thanks for the review and merge! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR introduce?
Simplify readme, because after #341 the
GITHUB_TOKENinput parameter isn't needed unless customizing the token, verified by @kdeldycke:GITHUB_TOKENdefault value inaction.yml#341 (comment)TODO:
GITHUB_TOKENin readmeGITHUB_TOKENfor token customization workaroundRelated issues
GITHUB_TOKENdefault value inaction.yml#341