2- [ ] Meaningful commit message, eg `add my-cool-package` (please don't mention `build-constraints.yml`)
3- [ ] At least 30 minutes have passed since uploading to Hackage
4- [ ] On your own machine, you have successfully run the following command (find verify-package in the root of this repo):
6 ./verify-package $package # or $package-$version
8The script runs virtually the following commands in a clean directory:
10 stack unpack $package-$version # `-$version` is optional
12 rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
13 stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
18Our CI tries to line up build-constraints.yaml with the current state
19of Hackage. This means that failures that are unrelated to your PR may
20cause the check to fail. If you think a failure is unrelated you can
21simply ignore it and the Curators will let you know if there is
22anything you need to do.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list