Analysis of Feb 17 data showed 400+ workflow runs/day consuming ~398 billable minutes (~200 hours/month projected). Implemented targeted optimizations: High-impact changes: - sec-audit.yml: add path filters (Cargo.toml, src/**, crates/**, deny.toml); skip docs-only PRs - test-benchmarks.yml: move from every-push-to-main to weekly schedule; retention 30d -> 7d - pub-docker-img.yml: tighten PR smoke build path filters to Docker-specific files only - sec-codeql.yml: reduce from twice-daily (14 runs/week) to weekly Medium-impact changes: - ci-run.yml: merge lint + lint-strict-delta into single job; drop --release from smoke build - feature-matrix.yml: remove push trigger (weekly-only); remove redundant cargo test step - dependabot.yml: monthly instead of weekly; reduce PR limits from 11 to 5/month; group all deps Runner cost savings: - Switch 6 lightweight API-only workflows to ubuntu-latest (PR Labeler, Intake, Auto Responder, Check Stale, Check Status, Sync Contributors) - pr-check-status.yml: reduce from every 12h to daily New files: - docs/ci-cost-optimization.md: comprehensive analysis and revised architecture documentation - scripts/ci/fetch_actions_data.py: reusable GitHub Actions cost analysis script Estimated impact: daily billable minutes ~400 -> ~120-150 (60-65%% reduction), monthly hours ~200 -> ~60-75, Dependabot PRs ~44/month -> ~5 (89%% reduction)
42 lines
1.8 KiB
YAML
42 lines
1.8 KiB
YAML
name: PR Check Stale
|
|
|
|
on:
|
|
schedule:
|
|
- cron: "20 2 * * *"
|
|
workflow_dispatch:
|
|
|
|
permissions: {}
|
|
|
|
jobs:
|
|
stale:
|
|
permissions:
|
|
issues: write
|
|
pull-requests: write
|
|
runs-on: ubuntu-latest
|
|
uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10.2.0
|
|
with:
|
|
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
days-before-issue-stale: 21
|
|
days-before-issue-close: 7
|
|
days-before-pr-stale: 14
|
|
days-before-pr-close: 7
|
|
stale-issue-label: stale
|
|
stale-pr-label: stale
|
|
exempt-issue-labels: security,pinned,no-stale,no-pr-hygiene,maintainer
|
|
exempt-pr-labels: no-stale,no-pr-hygiene,maintainer
|
|
remove-stale-when-updated: true
|
|
exempt-all-assignees: true
|
|
operations-per-run: 300
|
|
stale-issue-message: |
|
|
This issue was automatically marked as stale due to inactivity.
|
|
Please provide an update, reproduction details, or current status to keep it open.
|
|
close-issue-message: |
|
|
Closing this issue due to inactivity.
|
|
If the problem still exists on the latest `main`, please open a new issue with fresh repro steps.
|
|
close-issue-reason: not_planned
|
|
stale-pr-message: |
|
|
This PR was automatically marked as stale due to inactivity.
|
|
Please rebase/update and post the latest validation results.
|
|
close-pr-message: |
|
|
Closing this PR due to inactivity.
|
|
Maintainers can reopen once the branch is updated and validation is provided.
|