Add a CI check for building with Cabal #2445
Merged
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
The idea is that this ensures 1. that it's easy for contributers to hack on PostgREST without getting nix set up 2. we see things break more easily outside the very controlled nix environment (e.g. it would be easy to add a GHC 9.4.2 build here)
steve-chavez
approved these changes
Aug 24, 2022
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.
The idea is that this ensures
getting nix set up
environment (e.g. it would be easy to add a GHC 9.4.2 build here,
or to see some problems with the version bounds)
I wanted to have a check like this around while working on #2444, to ensure that that forked dependency doesn't cause cabal builds to fail.