Repository navigation
Initialize the changelog before shared workflow adoption - #3
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.
Prepare the existing changelog baseline before enabling fragment enforcement. Preserve every existing note and archive. The follow-up caller migration must be reviewed separately against this baseline so its strict no-direct-edits gate starts with a valid history.
Tracks #2. This baseline PR contains only the changelog initialization or pending-section normalization. The published shared validator accepts it; existing note bodies and archived history are preserved. The adoption PR will target this branch until this baseline merges, then must be retargeted and checked again.