Azure/azure-sdk-for-rust GitHub Actions scorecardPublic GitHub Actions data, last 30 days. Updated .
Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.
Biggest wins first, each with the exact config fix.
GitHub Event ProcessorAdd a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueVerify LinksAdd a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueGitHub Scheduled Event ProcessorAdd a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueAnalyzeThe schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.
on:
schedule:
- cron: '22 12 * * *' # was '0 12 * * *' — any non-:00 minute avoids the herdAnalyzeThe schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestCopilot Setup StepsNo job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Copilot Setup StepsThe cache restores only on an exact key match, so any lockfile change means a full cold download. Add a `restore-keys:` prefix line for partial restores.
key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
restore-keys: |
deps-${{ runner.os }}-Copilot Setup StepsThe schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.
on:
schedule:
- cron: '36 2 * * 1' # was '0 2 * * 1' — any non-:00 minute avoids the herdCopilot Setup StepsThe schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestGitHub Event ProcessorNo job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15GitHub Event Processor`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7GitHub Scheduled Event ProcessorNo job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15GitHub Scheduled Event Processor`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7GitHub Scheduled Event ProcessorThe schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.
on:
schedule:
- cron: '45 1 * * *' # was '0 1 * * *' — any non-:00 minute avoids the herdGitHub Scheduled Event ProcessorThe schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestVerify LinksNo job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Verify LinksRuns on every push/PR with no `paths:` filter, so docs-only changes still trigger full CI. Add a `paths:` filter if that's common.
on:
pull_request:
paths:
- 'src/**'
- 'package.json'# No concurrency control (applies to: GitHub Event Processor, Verify Links, GitHub Scheduled Event Processor)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# Scheduled at the top of the hour (applies to: Analyze)
on:
schedule:
- cron: '22 12 * * *' # was '0 12 * * *' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: Analyze, Copilot Setup Steps, GitHub Scheduled Event Processor)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# No job timeout (applies to: Copilot Setup Steps, GitHub Event Processor, GitHub Scheduled Event Processor, Verify Links)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Cache without restore-keys (applies to: Copilot Setup Steps)
key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
restore-keys: |
deps-${{ runner.os }}-
# Scheduled at the top of the hour (applies to: Copilot Setup Steps)
on:
schedule:
- cron: '36 2 * * 1' # was '0 2 * * 1' — any non-:00 minute avoids the herd
# Artifacts at default retention (applies to: GitHub Event Processor, GitHub Scheduled Event Processor)
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7
# Scheduled at the top of the hour (applies to: GitHub Scheduled Event Processor)
on:
schedule:
- cron: '45 1 * * *' # was '0 1 * * *' — any non-:00 minute avoids the herd
# No path filters on triggers (applies to: Verify Links)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.
This scorecard is a one-time snapshot. Install the free GitHub App to track this repo continuously: new regressions caught as they land, trends over time, on your public and private repos. Team adds the offending commit on the PR + Slack alerts.
Install & monitor this repo →💬 On Team, this same analysis posts automatically to every PR: the regression, and the exact commit that caused it, right where your team already looks. See plans →
Not ready to install? Get this report by email. No spam, unsubscribe anytime.