Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from Travis CI to Github Actions, improve CI generally #128

Open
langston-barrett opened this issue Oct 17, 2020 · 2 comments
Open
Labels

Comments

@langston-barrett
Copy link
Collaborator

Having an auto-generated CI build (using haskell-ci) has served us well as a starting point, but issues #67 and #126 demonstrate that we need some customization that's not available in that tool. Specifically, the ideal CI workflow would:

  1. Test with all supported versions of GHC, with an optionally-passing build of GHC pre-releases
  2. Build and upload releases (tags) to Github
  3. Test the Stack, Cabal, and Nix builds
  4. Run hlint and ormolu over the codebase
  5. Build and test the code with -Wall and -Werror
@langston-barrett
Copy link
Collaborator Author

See #133

@langston-barrett
Copy link
Collaborator Author

#133 tests with all supported versions of GHC, and runs hlint

#136 runs ormolu, see also #126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant