feat: auto-enable Actions on repos with repo-scoped RunnerPools #17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/auto-enable-actions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Before requesting a registration token for a repo-scoped RunnerPool,
the controller now calls PATCH /api/v1/repos/{owner}/{repo} with
has_actions=true. This is idempotent and ensures the registration
token API (which returns 405 when Actions is disabled) works without
manual repo setup.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Before requesting a registration token for a repo-scoped RunnerPool, the controller now calls PATCH /api/v1/repos/{owner}/{repo} with has_actions=true. This is idempotent and ensures the registration token API (which returns 405 when Actions is disabled) works without manual repo setup. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>Automated review by pr-reviewer v0.15.0 | Safety Check | anthropic | tracking id
r-c615c5-116acbThis is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — The change adds a reasonable feature to auto-enable Actions on repositories before requesting registration tokens, with proper error handling and validation.
Complexity: moderate
Safety Check Review
The change adds functionality to automatically enable Actions on repositories when creating repo-scoped RunnerPools. This prevents the registration token API from failing with a 405 error when Actions is disabled.
Key observations:
No security or correctness issues found. The implementation follows good practices with proper error handling and input validation.