nsaspy/zara-plugins
1
0
Fork 0
Code Issues 10 Pull requests 297 Projects Releases Packages Wiki Activity Actions

zara-coding: add index-only stale-safe commits #463

Open
nsaspy wants to merge 5 commits from rage/1-zara-coding-commit into main
pull from: rage/1-zara-coding-commit
merge into: nsaspy:main
Conversation 0 Commits 5 Files changed 5 +239 -3
nsaspy commented 2026-09-08 02:20:02 +00:00
Owner
Copy link

Advances #1 and fills the initial git.commit surface without exposing generic command execution.

Adds approval-gated coding.git.commit with a deliberately narrow contract:

  • commits exactly the already-staged index; never auto-stages files;
  • requires an attached local branch and caller-supplied full expected HEAD object ID;
  • rejects stale HEAD before writing a tree/commit object;
  • rejects an index tree identical to the parent tree;
  • bounds the commit message and passes it over stdin;
  • uses git write-tree + git commit-tree, not git commit, so repository commit hooks are not executed;
  • advances the current branch only with git update-ref <ref> <new> <expected> compare-and-set semantics;
  • all subprocesses remain fixed argv, bounded, and shell=False.

Low-level commit/update-ref behavior was also verified against a real temporary Git repo. RED-first commit 8d01ca34; implementation/tool/surface/docs follow. Full registry/plugin/Nix CI required before merge.

Advances #1 and fills the initial `git.commit` surface without exposing generic command execution. Adds approval-gated `coding.git.commit` with a deliberately narrow contract: - commits exactly the already-staged index; never auto-stages files; - requires an attached local branch and caller-supplied full expected HEAD object ID; - rejects stale HEAD before writing a tree/commit object; - rejects an index tree identical to the parent tree; - bounds the commit message and passes it over stdin; - uses `git write-tree` + `git commit-tree`, not `git commit`, so repository commit hooks are not executed; - advances the current branch only with `git update-ref <ref> <new> <expected>` compare-and-set semantics; - all subprocesses remain fixed argv, bounded, and `shell=False`. Low-level commit/update-ref behavior was also verified against a real temporary Git repo. RED-first commit `8d01ca34`; implementation/tool/surface/docs follow. Full registry/plugin/Nix CI required before merge.
docs(zara-coding): document index-only stale-safe commit
Some checks failed
CI / test (pull_request) Failing after 18s
Details
771d66e503
Some checks failed
CI / test (pull_request) Failing after 18s
Details
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/README.md
  • plugins/zara-coding/lib/zara_coding/domain.py
  • plugins/zara-coding/test/test_plugin.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/1-zara-coding-commit:rage/1-zara-coding-commit
git switch rage/1-zara-coding-commit

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/1-zara-coding-commit
git switch rage/1-zara-coding-commit
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-commit
git switch rage/1-zara-coding-commit
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-commit
git switch main
git merge --squash rage/1-zara-coding-commit
git switch main
git merge --ff-only rage/1-zara-coding-commit
git switch main
git merge rage/1-zara-coding-commit
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
security

   
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara-plugins!463
No description provided.