Make github_token optional
#61
Merged
Conversation
This file contains 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
|
@asbjornu Thanks for spotting this. Feel free to merge it under the major, minor or patch labels. |
|
I prefer the |
I agree, but I'm not certain I understand what you mean by "label". As in conventional commits or by manually creating a |
|
Ah sorry for being so unclear, it was related to the git label used by the release action. This will create the tag automatically when the pull request is merged. |
|
🚀 [bumpr] Bumped! New version:v5.1.0 Changes:v5.0.2...v5.1.0 |
|
Ah, right. Thanks, @rickstaa! 🙏🏼 |
asbjornu
added a commit
that referenced
this pull request
Nov 30, 2021
Update documentation for `github_token` now that #61 is merged.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make
github_tokenoptional. Resolves #60.