The gate reads what the forge would merge now from the seat git's pull, so it names no forge tool (milestone 47/G, W11.18 follow-up)
The base's protection and required contexts, the forge's conflict word and the merging account's write access come from the pull answer's merging (issues 1275, 1945; ADR 0441 §1); a required context not a success at the commit blocks. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ (Joined from 13e12d2c.) Builds: design 47 G §252, §310, §312 (GATE14) Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
This commit is contained in:
@@ -257,7 +257,6 @@
|
||||
"seat:git.statuses",
|
||||
"seat:git.open-pulls",
|
||||
"seat:git.contains",
|
||||
"gitea.gitea_commit_statuses",
|
||||
"seat:mesh-hand-acts.hand-act"
|
||||
],
|
||||
"state": [
|
||||
|
||||
Reference in New Issue
Block a user