chore: PR-only CI trigger + concurrency cancel - #76
Merged
Conversation
Drop the redundant push:main trigger and add a concurrency block. ci ran on both push and pull_request, double-billing every PR (PR run + squash-merge run). The required check (where present) is satisfied by the PR run; deploys are handled separately (platform-driven or via a dedicated deploy.yml). Part of the cross-repo Actions cost cleanup documented in ~/.claude/knowledge-base/github-actions-cost-control.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
railway-app
Bot
temporarily deployed
to
Breadcrumbs / breadcrumbs-pr-76
May 26, 2026 06:08
Destroyed
|
🚅 Deployed to the breadcrumbs-pr-76 environment in Breadcrumbs
|
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
1 participant
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.
Cross-repo GitHub Actions cost cleanup.
ci.ymlran on bothpush: mainandpull_request: main, double-billing every PR — once on the PR head, again on the squash-merge commit. The required check (where present) is satisfied by the PR run; deploys are handled separately (platform-driven on Railway/Render, or via a dedicateddeploy.ymlon homebase). Also addsconcurrency: cancel-in-progressso rapid fixup pushes don't stack parallel runs.Full playbook:
~/.claude/knowledge-base/github-actions-cost-control.md.🤖 Generated with Claude Code