Skip to content

Commit 12b4c76

Browse files
committed
docs: add ARC GitHub App Actions permission to lessons learned
The GitHub docs don't mention this requirement, but without Actions: Read and write permission, runners receive no job events and sit idle.
1 parent 470366c commit 12b4c76

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

.github/copilot-instructions.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,3 +51,10 @@ Document any issues that took multiple attempts to resolve here for future refer
5151
To use with docker-build.yml, set `runs_on: tak-k8s-ci` to run on self-hosted K8s runners. The workflow will automatically try the central BuildKit at `tcp://buildkit.buildkit.svc.cluster.local:1234` before falling back to docker-container driver.
5252
5353
Without central BuildKit, each build starts cold with no cache. Registry cache (`cache-from=type=registry`) helps but is slower than local cache due to network I/O.
54+
55+
- **ARC GitHub App requires Actions permission**: The GitHub documentation for ARC authentication (https://docs.github.com/en/actions/tutorials/use-actions-runner-controller/authenticate-to-the-api) does NOT mention this, but the GitHub App **must** have **Actions: Read and write** permission under Repository Permissions. Without it, the listener receives no job events and runners sit idle showing "Waiting for a runner to pick up this job" forever, even though runners are connected and listening. Symptoms:
56+
- Listener logs show `"assigned job": 0` continuously
57+
- Runner logs show "Connected to GitHub" and "Listening for Jobs"
58+
- GitHub UI shows "Waiting for a runner to pick up this job"
59+
60+
Fix: Go to GitHub App settings → Permissions → Repository permissions → Actions → set to "Read and write".

0 commit comments

Comments
 (0)