Repository navigation
chore(cli): format staged source before commits - #10
Merged
Merged
Conversation
Format staged source and configuration before Git records a commit. Run formatters against index bytes and replace staged blobs atomically so partial staging retains unstaged edits and unrelated index entries. Prepare pinned formatter tools during setup and keep downloads out of commit hooks. Preserve the repository's existing check and message hooks, and retain generated outputs under their canonical generators. Co-authored-by: Codex <noreply@openai.com>
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.
TL;DR
Format staged source and configuration before commits while preserving unstaged
edits and unrelated index entries.
Changes
Use the locked shared staged-blob engine with pinned formatter routes for this
repository's source and configuration. Prepare tools during setup, retain
existing Git checks, and stop a commit without partial index updates when a
formatter fails. Generated files retain their canonical generator output.
Validation: a real installed-hook commit formatted Markdown and representative source with a minimal system PATH, preserved disjoint unstaged edits and unrelated files, and left the index consistent with the recorded commit. Shared regression tests cover repeat setup, retained hook checks, modified-hook protection and formatter failure rollback. All 142 Python tests passed after resolving the pinned Swift package. Local results cover the formatter-hook changes; hosted validation remains separate.
Follow-ups and Next Work
None within this change. Provider state, production deployment, publication and
release acceptance remain governed by their existing workflows.