... | ... | @@ -74,6 +74,20 @@ The *Pipelines* tab provides a more detailed overview on the state of the variou |
|
|
|
|
|
Finally, the *Changes* tab shows the patch itself. This view may be restricted to changes made by a single commit by selecting the commit in the *Commits* tab. Moreover, one may view previous iterations of the merge request using the two drop-down menus at the top of the tab. To leave an inline comment click on a line in the patch.
|
|
|
|
|
|
### Modifying the validation pipeline
|
|
|
|
|
|
By default we run a selected few jobs in each merge request on the most common platforms.
|
|
|
|
|
|
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.
|
|
|
|
|
|
* ~"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.
|
|
|
* ~"test-bootstrap": Test the bootstrapping scripts to make sure we can build with several different boot compilers.
|
|
|
* ~"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.
|
|
|
|
|
|
|
|
|
## Merging your merge request
|
|
|
|
... | ... | |