Repository navigation
Clarify commit scope and release v0.6.2 - #14
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.
Commit runs can mistake an old instruction against editing a file for a restriction on committing the user's existing changes. Respect applicable remembered preferences while distinguishing past task scope, give current explicit instructions precedence, and require final commit/status verification with exclusion reasons. Request a combined progress update for routine work and warn before launch when Git cannot resolve explicit author and committer identities.
Prepare v0.6.2 metadata and download examples. Memory settings, Git configuration, hooks, and failure output remain intact.
Validation: formatting and workspace Clippy; all 96 automated tests; package publish dry-run and package-content inspection. Two live Codex runs with memory enabled verified intended commits, explicit exclusions, preserved staged changes, unchanged file contents, and pre-commit hooks. Independent review found no issues.