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

coding: make branch creation HEAD fence atomic #386

Open
nsaspy wants to merge 0 commits from rage/189-atomic-branch-create into main
pull from: rage/189-atomic-branch-create
merge into: nsaspy:main
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-08 02:19:39 +00:00
Owner
Copy link

Closes #189. Advances #1.

RAGE transaction.

RED 9a5f9fd1: branch creation must use one git update-ref --stdin transaction that verifies HEAD == expected_head and creates the new branch ref together; the old separate rev-parse HEAD precheck is forbidden.

RED was confirmed by exact-head CI: compatibility diagnostics passed, coding tests failed at the new atomic contract, package builds were skipped.

Sync 0af0a266: merged canonical main including #188 without losing the RED.

Implementation 8310dbfb: uses one canonical update-ref --stdin transaction with start, verify HEAD, create-only branch ref, prepare, and commit; full object-ID/ref validation remains unchanged.

Final gate: compatibility contracts, full generated registry/plugin nix flake check, generated package builds, zero unresolved review threads, exact-head protected merge.

Closes #189. Advances #1. RAGE transaction. RED `9a5f9fd1`: branch creation must use one `git update-ref --stdin` transaction that verifies `HEAD == expected_head` and creates the new branch ref together; the old separate `rev-parse HEAD` precheck is forbidden. RED was confirmed by exact-head CI: compatibility diagnostics passed, coding tests failed at the new atomic contract, package builds were skipped. Sync `0af0a266`: merged canonical `main` including #188 without losing the RED. Implementation `8310dbfb`: uses one canonical `update-ref --stdin` transaction with `start`, `verify HEAD`, create-only branch ref, `prepare`, and `commit`; full object-ID/ref validation remains unchanged. Final gate: compatibility contracts, full generated registry/plugin `nix flake check`, generated package builds, zero unresolved review threads, exact-head protected merge.
Some checks failed
CI / test (pull_request) Failing after 18s
Details
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/189-atomic-branch-create:rage/189-atomic-branch-create
git switch rage/189-atomic-branch-create

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/189-atomic-branch-create
git switch rage/189-atomic-branch-create
git rebase main
git switch main
git merge --ff-only rage/189-atomic-branch-create
git switch rage/189-atomic-branch-create
git rebase main
git switch main
git merge --no-ff rage/189-atomic-branch-create
git switch main
git merge --squash rage/189-atomic-branch-create
git switch main
git merge --ff-only rage/189-atomic-branch-create
git switch main
git merge rage/189-atomic-branch-create
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!386
No description provided.