FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

fix: make commit messages one-shot per worktree by qiankunli · Pull Request #106 · compforge/devloop · GitHub

fix: make commit messages one-shot per worktree - #106

Merged
qiankunli merged 1 commit into
mainfrom
fix/commit-msg-write
Jul 20, 2026
Merged

fix: make commit messages one-shot per worktree#106
qiankunli merged 1 commit into
mainfrom
fix/commit-msg-write

Conversation

Copy link
Copy Markdown
Collaborator

Standardize the canonical scratch path as .devloop/commit_msg and require full overwrite instead of editing previous contents.

Model the scratch as working-tree state so linked worktrees do not share commit input. Remove it only after a successful gcam/gcamp/gcampr flow, retain it after failures for retry, and leave caller-owned message files untouched.

Add lifecycle and scope coverage and bump the devloop plugin to 0.1.54.

Standardize the canonical scratch path as .devloop/commit_msg and require full overwrite instead of editing previous contents.

Model the scratch as working-tree state so linked worktrees do not share commit input. Remove it only after a successful gcam/gcamp/gcampr flow, retain it after failures for retry, and leave caller-owned message files untouched.

Add lifecycle and scope coverage and bump the devloop plugin to 0.1.54.
qiankunli merged commit fcb82b7 into main Jul 20, 2026
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL