Repository navigation
ci: only main pushes start the fork nightly - #130
Merged
Merged
Conversation
Pushes to any branch started a fork nightly run. Its jobs skipped, but the run still took the single pending slot of the fork-nightly-release concurrency group, so every PR-branch push cancelled main's queued nightly. On 2026-10-24 the nightly carrying #123/#125/#126 was cancelled twice this way. Trigger on pushes to main only; workflow_dispatch still works for other refs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
Every push to any branch started a fork nightly run. Its jobs skipped, but the run still took the single pending slot of the
fork-nightly-releaseconcurrency group, so each PR-branch push cancelled main's queued nightly. Today the nightly carrying #123/#125/#126 was cancelled twice (runs 40072672650, 40072695260).Fix: trigger on pushes to
mainonly.workflow_dispatchis unchanged.Claude Opus 5.5 via Claude Code (T3 Captain).
🤖 Generated with Claude Code