V0.7.3/git keep a changelog ii - #28
Merged
Merged
Conversation
Separate manifest-diff reading (4a–4b) from commit-body reading (4c) to ensure the skill captures the full cumulative dependency picture when multiple commits touched version files. Add test case 13 to validate this behavior handles multi-commit manifest updates correctly.
Add a mandatory Step 4a for concrete releases to inspect the base commit before reading manifests. The base commit often contains release-prep changes and version bumps that are foundational to the release narrative. Update all subsequent steps (4a→4b, 4b→4c, etc.) and clarify when to use <base>^..HEAD for concrete releases versus <base>..HEAD for unreleased changelogs. Add quality-gate reminder to never omit the base commit from concrete release changelogs.
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.
This pull request updates the changelog skill documentation to clarify and improve the process for handling concrete releases, especially regarding manifest and base commit inspection. The most important changes focus on ensuring that foundational changes in the base commit are always included in release changelogs and that the correct sequence is followed when processing dependency/version manifests.
Changelog process improvements:
## [X.Y.Z]) before any other steps, ensuring foundational version bumps and release-prep changes are included in the changelog. This is achieved by using the<base>^..HEADrange for concrete releases.Documentation and accuracy enhancements: