ci: GitHub Actions cost optimization#17
Merged
Merged
Conversation
…oncurrency, timeout)
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.
Standard cost-optimization sweep applied via cross-org audit on 2026-04-30.
Changes per workflow file ( enforce-release-source.yml ):
paths-ignorefor**.md,docs/**,.vscode/**,LICENSE,.gitignore,**.txt,.editorconfig,.prettierignore.concurrencyblock keyed on${{ github.workflow }}-${{ github.ref }}.cancel-in-progress: truefor non-prod,falsefor prod-deploy (CloudFormation safety).timeout-minutes: 30to any job lacking one (cap runaway runs).This is a defensive change — workflows on this repo currently fail or are stale, but if/when the pipeline is fixed and pushed to, the cost ceiling is now bounded.
Risks:
cancel-in-progress: trueon CI means rapid-fire pushes will cancel earlier runs (intended).paths-ignoreskips workflow runs on doc-only changes; code changes still trigger.timeout-minutes: 30may be too tight for some jobs — bump explicitly per job if so.No deploy/CI logic was changed; only metadata around when and how runs execute.