ci: fix release/next checkout so Automated Release can push it#36
Merged
Conversation
…ush it Prior fix removed the checkout, so the action's 'git push origin release/next' had no local ref (src refspec does not match). Create release/next from master HEAD, push it, and set its upstream to origin/release/next so both 'git pull --ff-only' and the explicit push succeed (never tracks master).
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
1 participant
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.
Second follow-up. #35 removed the branch checkout, so the changelog action's
git push origin release/nextfailed (src refspec release/next does not match any) when #33 merged - so v1.16.0 was NOT released. Fix: check outrelease/nextfrom master HEAD, pre-push it, and track origin/release/next (never master). Merging this re-triggers the release and should cut v1.16.0 (the #33 feat is still unreleased).