CI: skip docs-only changes and duplicate runs - #26
Merged
Merged
Conversation
push builds only main and both triggers ignore Markdown, specs/, LICENSE and .gitignore — changes that cannot affect the build. The trigger edit is stored as .github/haskell-ci.patch and wired into cabal.haskell-ci (github-patches), so haskell-ci regenerate re-applies it instead of reverting it.
A new push to a branch or PR cancels the previous in-flight run via a concurrency group; runs on main always complete. Captured in .github/haskell-ci.patch alongside the trigger changes.
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
1 participant
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.
Two trigger changes to the Haskell-CI workflow, no job changes:
pushandpull_request:**.md,specs/**,LICENSE,.gitignore— a change touching only those files cannot affect the build, so the 5-compiler matrix is skipped. A PR touching both docs and code still runs (paths-ignore only skips when every changed file matches). Note the golden corpus.jsonfiles are deliberately not ignored — they are test inputs.pull_requestonly, and main builds on merge.merge_groupandworkflow_dispatchare unchanged (dispatch remains the manual escape hatch to force a run).Safe because
mainhas no required status checks (verified — no branch protection), so a skipped workflow can't wedge a merge as eternally 'Expected'.Regeneration-proofing: the workflow is haskell-ci-generated, so a bare hand edit would be reverted by the next
haskell-ci regenerate(e.g. adding a GHC version). The trigger edit is therefore also captured as.github/haskell-ci.patchand wired up viagithub-patchesin a newcabal.haskell-ci, which haskell-ci re-applies after generating.This PR touches the workflow file itself, so CI runs on it — which validates the new trigger YAML parses.