clawbot
13125ac6f5
check / check (push) Failing after 1s
Every PR here adds an entry at the top of Completed Steps in `TODO.md`, so each merge to `next` left the other open PRs conflicting there. A root `.gitattributes` now marks `TODO.md` with `merge=union`: when two branches insert at the same place, git keeps both sides. It applies to this repository only; nothing canonical changes. Union never reports a conflict in `TODO.md`. When two new entries share an identical line, one can land inside the other, and a rebased entry sits below every entry that reached `next` after the branch was cut, so the merged entries are read after every merge or rebase. Whether Gitea's own conflict check applies the attribute is not known. Model: opus-5-5
5 lines
225 B
Plaintext
5 lines
225 B
Plaintext
# Every PR adds an entry at the top of TODO.md's Completed Steps; union keeps
|
|
# both sides instead of conflicting. Git never reports a conflict here: read
|
|
# the merged entries after every merge or rebase.
|
|
TODO.md merge=union
|