Separate workflow for checks #1052
Closed
Conversation
This file contains 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
phadej
force-pushed
the
separate-workflow-for-checks
branch
from
28c6989 to
23cb160
Compare
I'm experimenting with an idea of generating a separate workflow for checks which are enough to do once. E.g. hlint is run once. `cabal check` does the same for every GHC. Having such checks in a separate workflow, would: - allow per-GHC builds to pass even if there is e.g HLint issue - allow more parallism - simplify structure The goal is that `haskell-ci` would be able to generate `lints.yml` file too, as it looks there are potentially a lot of setup to do.
phadej
force-pushed
the
separate-workflow-for-checks
branch
from
23cb160 to
c35aa38
Compare
|
Checks are tricky, I'll make another PR if I make any progress. |
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.
I'm experimenting with an idea of generating a separate workflow for checks which are enough to do once. E.g. hlint is run once.
cabal checkdoes the same for every GHC.Having such checks in a separate workflow, would:
The goal is that
haskell-ciwould be able to generatelints.ymlfile too, as it looks there are potentially a lot of setup to do.