merge: bring the README layout and the branch claim back to the code

2026-08-10 20:07:23 +05:00
parent f97ac952f7 edb2f5a627
commit 81119a3bd9
2 changed files with 49 additions and 13 deletions
@@ -355,8 +355,11 @@ A milestone must already exist in the repo — push attaches, it does not create

 `branch:` is Gitea's `ref`, the branch the work actually lives on. Push fills
 an empty one with the current git branch (`git rev-parse --abbrev-ref HEAD`)
-and writes it back into the issue file; a value already there is never
-overwritten, neither on create nor on `--update`. On a detached HEAD or outside
+and sends it up as `ref`; a value already there is never
+overwritten, neither on create nor on `--update`. Nothing is written back to
+the issue file — there is no file left to write to, because a successful push
+deletes it. The branch comes back on disk with the next `pull.py <n>`, from
+the tracker. On a detached HEAD or outside
 a git repo no `ref` is sent and a warning names the issues that went up without
 one. Reading the branch is the only thing these scripts ask git for — they
 never check out, create, or write anything.