Repository navigation
docs(memory): log the release-flow lesson - #5
Merged
Merged
Conversation
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
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.
The 0.1.2 release was carried out half by the book: the version bump went through PR #4 (green CI,
--merge), then the CHANGELOG and the tag were pushed straight tomain— whichfuse-commit-pro:git-flowforbids outright.Because the workflow also listens on
push: [main], CI went green after the fact and the process defect stayed invisible:v0.1.2tags a commit nobody reviewed.Records the lesson: the CHANGELOG and the bump belong to the feature branch, before the merge — that is exactly why the merge is
--mergeand never--squash, so the tag points at a bump commit that went through the PR.No history rewrite:
mainis never force-pushed. The tagged commit is functionally correct and its CI is green; only the path was wrong.