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.
Addresses changesets/changesets#1545
When
createGithubReleases
istrue
, the action doesn't push the tags created locally by thepublish
command.Instead, it creates tags through the
createRelease
api and provides thetarget_commitish
value.Tested running this in one of my repos, and it worked by providing a token generated from a GitHub App. However, I guess this would be breaking in some way, as it won't push tags unless there is a release generated by the release notes.
I think I could make it non-breaking by adding an input that specifically enables this behavior. Unsure what I would name it, maybe
createTagsThroughReleases
. I'd love some feedback on how this should be implemented if this is desired functionality, before I continue working on this.