Repository navigation
Keep Repo Assist maintaining PRs when the scheduled PR cap is reached - #407
Merged
Merged
Conversation
Select maintenance and triage at capacity instead of rejecting activation, and validate live capacity before creating scheduled PR batches. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Oct 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replace Repo Assist's whole-run scheduled PR-cap gate with maintenance-only mode. At eight open
[repo-assist]PRs, the old activation check stopped everything—including Task 6, which maintains existing PRs. This was observed in fsprojects/Paket's October 17 run.This branch is independently based on
main, not stacked on the separate output-consistency change.Validation
python3 -m unittest discover -s tests -p 'test_repo_assist_*.py' -v: 12 passed.gh aw compile workflows/repo-assist.md --approve: passed with gh-aw v0.93.3; freshness reports Yes.process_safe_outputsand is schedule-only.git diff --check: passed.The compiler reports ten warnings in its generated scaffolding (including undeclared admission outputs and persisted-checkout credentials). They are not suppressed here. Sample
workflows/*.lock.ymlfiles are intentionally ignored in this repository, so the regenerated lock is validated locally rather than force-added. Shared action-cache churn was excluded.Compiler compatibility / security review
Compilation with the current release required removing the unsupported native Copilot
web-fetchentry and normalizingrequest_reviewtorequest-review. Existing allowed networking and shell tools remain available; no agent write permission is added.The new authored action use is
actions/download-artifact@v8, resolved by compilation to9000827ccba6bdab643e8b6fd33ac0654aef8333(v8.0.2), whose tag was verified. The generated setup pin is gh-aw-actions v0.93.3 (e89a5670dc4c790b37ade361215b8d72d8ce8942), also verified. No new secrets or redirect changes.GH_TOKENuses the existing GitHub token only for read-only API calls. The guard parses JSON artifacts; it does not execute their contents. The existing memory validator is unchanged; the current compiler's newly recorded validator approval was reviewed.Hosted CI result
CI run 40114441375 ran all 12 new regression tests successfully. The subsequent repository-wide compile failed on unchanged
.github/workflows/daily-repo-goals.mdand.github/workflows/link-checker.md, whose nativetools.web-fetchentries are rejected by the latest compiler. Neither file is modified by this PR. The updated Repo Assist template compiles successfully in focused local validation. This unrelated compatibility upgrade is intentionally not bundled here.Companion independent PR: #406.