... | ... | @@ -80,7 +80,7 @@ By default we run a selected few jobs in each merge request on the most common p |
|
|
|
|
|
When your patch is tested for merging by marge bot the full pipeline is run, which may show additional unanticipated failures in your patch.
|
|
|
|
|
|
There are a few labels that you can apply to modify the configurations which are tested on a merge request pipeline.
|
|
|
You can use *labels* to modify the configurations which are tested on a merge request pipeline.
|
|
|
|
|
|
* ~"full-ci": Run a complete validation pipeline which tests many more architectures and configurations
|
|
|
* ~"user-facing": Run head.hackage on your MR to test any user-facing changes which might affect libraries.
|
... | ... | @@ -88,6 +88,7 @@ There are a few labels that you can apply to modify the configurations which are |
|
|
* ~"test-reinstall": Test the cabal-reinstall job, which checks that we can build all the packages using a vanilla cabal.
|
|
|
* ~"test-primops": Run test-primops, a testsuite which generates randomised tests for primops.
|
|
|
|
|
|
You apply a label using the "Labels" button in the right hand column.
|
|
|
|
|
|
## 5. Merging your merge request
|
|
|
|
... | ... | |