GitSpider

go-gorm/gorm GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated 7/1/2026, 10:27:44 PM.

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 9 patterns
Rough estimate from wall-clock run time at standard Linux pricing. Public repos run Actions free, so the dollar figures are the equivalent cost on a private repo. Matrix/parallel jobs and your actual runners will differ.
0.2%
failure rate, 30d
0m
avg time to recover from a failure
10 workflows · 500 runs (16.7/day) · 168 CI-min (wall-clock) · ≈$1 at private-repo rates (30d)
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

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 →

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 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 →

No job timeout · Stale

~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 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 >4×/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.

on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

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 >4×/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.

on:
  schedule:
    - cron: '*/30 * * * *'  # every 30 min instead of every minute

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 →

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 →

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

Share this scorecard: https://gitspider.com/scan/go-gorm/gorm
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)