Repository navigation
ci: cut runner time without dropping the required checks - #35
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runner time, not money: the repository is public, so minutes are free. These changes cut the wall-clock and the queue that every push pays.
What changes
actions, go, javascript, javascript-typescript, python, typescripttogo, actions, javascript-typescript. The repository contains no Python, and the JavaScript/TypeScript pair was analysed twice. Three of six analyses per push produced no signal.ci.ymlconcurrency:ci-<workflow>-<ref>withcancel-in-progress, so a new push supersedes the run it replaced.ci.ymlpath filter inside the jobs, never at workflow level: achangesjob compares the diff (origin/<base>...HEADfor PRs,before..afterfor pushes) and only the heavy steps are gated on it. The jobs themselves still run and still reporttest (1.22),test (1.24)andgoreleaser-check, because those are the required checks onmainand a skipped job leaves them unsatisfied. An unknown diff (new branch, forced push, manual run) runs the Go steps rather than skipping them. Changes to.github/workflows/,go.mod,go.sum,Makefile,action.yml,.goreleaser.ymlandscripts/all count as Go-relevant.setup-gomodule cache enabled in both matrix legs and the goreleaser job.pages.yml: dropped the separatenpm run typecheck, because the export build runs TypeScript itself (its log prints "Running TypeScript"). Lint still runs before the build.Verification
The workflow YAML is exercised by this PR itself: the
changesjob runs, and because the diff touches.github/workflows/, bothtestlegs andgoreleaser-checkexecute in full. The skip path will be exercised by the next website-only change.Not done
Workflow-level
paths-ignoreonci.ymlwould skip the jobs entirely and leave the three required checks unreported, which blocks every PR. That is why the filter sits inside the job.

Confidence Score: 5/5
The PR appears safe to merge; the previous CI failure is fixed.Summary
This PR cuts CI work by filtering Go-related changes, caching Go modules, cancelling replaced runs, and removing the separate website typecheck.
Reviews (2) · Last reviewed commit: "ci: keep full history for the diff and f..." · Reviewed by Greptile