go-gorm/gorm GitHub Actions scorecard

Public 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.

12 min/mo
recoverable (~7% of CI time) · across 14 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 14 fixes, each with the exact YAML ↓
1.2%
failure rate, 30d
3m
avg time to recover from a failure
9 workflows · 2,500 runs (83.3/day) · 179 CI-min (wall-clock) · ≈$1 at private-repo rates (30d)
CI minutes, cost and failure rate are from the latest 500 of 2,500 runs.

Where the minutes go (30d)

Close Missing Playground issues~57 min · 238 runs
Close invalid questions issues~56 min · 240 runs
tests~49 min · 7 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · Close invalid questions issues

~6 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Full guide: how to fix this →

No concurrency control · Close Missing Playground issues

~6 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

Full guide: how to fix this →

Also found: 12 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

No job timeout · golangci-lint

~0 min/mo

No 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: 15

Full guide: how to fix this →

No job timeout · Close invalid questions issues

~0 min/mo

No 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: 15

Full guide: how to fix this →

Frequent scheduled runs · Close invalid questions issues

~0 min/mo

A 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

Full guide: how to fix this →

Scheduled workflow runs in forks · Close invalid questions issues

~0 min/mo

The 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-latest

Full guide: how to fix this →

No job timeout · Issue Labeler

~0 min/mo

No 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: 15

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · Issue Labeler

~0 min/mo

1 third-party action pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: jinzhu/super-labeler-action@<full-sha>  # was @develop

No job timeout · Close Missing Playground issues

~0 min/mo

No 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: 15

Full guide: how to fix this →

Frequent scheduled runs · Close Missing Playground issues

~0 min/mo

A 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

Full guide: how to fix this →

Scheduled workflow runs in forks · Close Missing Playground issues

~0 min/mo

The 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-latest

Full guide: how to fix this →

No job timeout · tests

~0 min/mo

No 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: 15

Full guide: how to fix this →

Cache without restore-keys · tests

~0 min/mo

The 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 }}-

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · tests

~0 min/mo

1 third-party action pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead.

uses: Icemap/tidb-action@<full-sha>  # was @main
Copy every fix as one block (7 snippets, annotated per workflow)
# No concurrency control (applies to: Close invalid questions issues, Close Missing Playground issues)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: golangci-lint, Close invalid questions issues, Issue Labeler, Close Missing Playground issues, tests)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Frequent scheduled runs (applies to: Close invalid questions issues, Close Missing Playground issues)
on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

# Scheduled workflow runs in forks (applies to: Close invalid questions issues, Close Missing Playground issues)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# Third-party actions pinned to a mutable ref (applies to: Issue Labeler)
uses: jinzhu/super-labeler-action@<full-sha>  # was @develop

# Cache without restore-keys (applies to: tests)
    key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
    restore-keys: |
      deps-${{ runner.os }}-

# Third-party actions pinned to a mutable ref (applies to: tests)
uses: Icemap/tidb-action@<full-sha>  # was @main

Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.

Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/go-gorm/gorm.svg)](https://gitspider.com/scan/go-gorm/gorm)

Want this on every push?

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, every PR gets an automatic comment when its CI run fails or runs slow, right where your team already looks. See plans →

Not ready to install? Get this report by email. No spam, unsubscribe anytime.

Share this scorecard: https://gitspider.com/scan/go-gorm/gorm