@@ -1,5 +1,5 @@
2−- [ ] Meaningful commit message, eg `add my-cool-package` (please not mention `build-constraints.yml`)
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
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):
4- [ ] On your own machine, you have successfully run the following command (find verify-package in the root of this repo):
@@ -11,3 +11,12 @@ The script runs virtually the following commands in a clean directory:
11 cd $package-$version
11 cd $package-$version
12 rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
12 rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
13 stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
13 stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
18+Our CI tries to line up build-constraints.yaml with the current state
19+of Hackage. This means that failures that are unrelated to your PR may
20+cause the check to fail. If you think a failure is unrelated you can
21+simply ignore it and the Curators will let you know if there is
22+anything you need to do.