Running-test-pipelines-for-merge-requests.md

+Test pipelines automatically run the dumux test suite in different configurations including the changes of the merge request. To activate the testing, look for a banner like the following on the page of your merge request:
+
+![Screenshot_2022-05-12_at_19.45.20](uploads/7cb766e9fc8239952bb7dc39b824f1f2/Screenshot_2022-05-12_at_19.45.20.png)
+
+This means that test pipelines have been created but there is _manual_ action required (that is manually starting the pipeline so it actually runs the tests). In order to start the pipeline(s) click on the cog on the left. You will then see something like this
+
+![Screenshot_2022-05-12_at_19.48.41](uploads/fe223df58fb4ee0fbed956e82576ecb2/Screenshot_2022-05-12_at_19.48.41.png)
+
+You can start all pipelines together by clicking the play button next to "Trigger dumux pipelines". You can also start individual pipelines (for an intermediate test to save computational resources and time) by clicking the play button next to the pipeline. The pipelines use different combinations of dune and dumux versions and compilers.
+
+In order for a merge request to get merged, all pipelines need to pass (green tick).
\ No newline at end of file