BL-Operations/blc-cron-sync 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.
🏆 You're Top 25%. Show it off in your README:
[](https://gitspider.com/scan/BL-Operations/blc-cron-sync)Biggest wins first, each with the exact config fix.
Coverage Zips Sync (Tableau Extract + Salesforce)Set `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.
- uses: actions/setup-node@v4
with:
node-version: 20
cache: 'npm'Salesforce Account ExtractionAdd a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueCampaign Group SyncSet `cache: 'npm'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.
- uses: actions/setup-node@v4
with:
node-version: 20
cache: 'npm'Campaign Group SyncNo 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: 15Campaign Group SyncThe 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-latestCoverage Zips Sync (Tableau Extract + Salesforce)The 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: '10 */4 * * *' # was '0 */4 * * *' — any non-:00 minute avoids the herdSalesforce Account ExtractionA schedule cron fires >4x/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.
on:
schedule:
- cron: '*/30 * * * *' # every 30 min instead of every minute# Missing dependency cache (npm) (applies to: Coverage Zips Sync (Tableau Extract + Salesforce), Campaign Group Sync)
- uses: actions/setup-node@v4
with:
node-version: 20
cache: 'npm'
# No concurrency control (applies to: Salesforce Account Extraction)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No job timeout (applies to: Campaign Group Sync)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Scheduled workflow runs in forks (applies to: Campaign Group Sync)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# Scheduled at the top of the hour (applies to: Coverage Zips Sync (Tableau Extract + Salesforce))
on:
schedule:
- cron: '10 */4 * * *' # was '0 */4 * * *' — any non-:00 minute avoids the herd
# Frequent scheduled runs (applies to: Salesforce Account Extraction)
on:
schedule:
- cron: '*/30 * * * *' # every 30 min instead of every minuteEach 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.