#211 extracted the robot to scripts/merge_robot.py but the workflow never got an actions/checkout step. Every robot run since inception: python3: can't open file .../scripts/merge_robot.py: No such file or directory → exit 2. The 18 loud failures were NOT the auth fix working — the script never ran at all.
Stack: (1) #213 fixed reserved-secret auth (GITEA_TOKEN is the read-only auto token); (2) this PR adds the missing checkout. First real robot run expected after merge.
Acceptance
Next robot run log must show: merge-robot: authenticated as conductor + per-PR decision lines (merged/skipped).
## Second stacked root cause
#211 extracted the robot to `scripts/merge_robot.py` but the workflow never got an `actions/checkout` step. Every robot run since inception: `python3: can't open file .../scripts/merge_robot.py: No such file or directory` → exit 2. The 18 loud failures were NOT the auth fix working — the script never ran at all.
Stack: (1) #213 fixed reserved-secret auth (GITEA_TOKEN is the read-only auto token); (2) this PR adds the missing checkout. First real robot run expected after merge.
## Acceptance
Next robot run log must show: `merge-robot: authenticated as conductor` + per-PR decision lines (merged/skipped).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Second stacked root cause
#211 extracted the robot to
scripts/merge_robot.pybut the workflow never got anactions/checkoutstep. Every robot run since inception:python3: can't open file .../scripts/merge_robot.py: No such file or directory→ exit 2. The 18 loud failures were NOT the auth fix working — the script never ran at all.Stack: (1) #213 fixed reserved-secret auth (GITEA_TOKEN is the read-only auto token); (2) this PR adds the missing checkout. First real robot run expected after merge.
Acceptance
Next robot run log must show:
merge-robot: authenticated as conductor+ per-PR decision lines (merged/skipped).