diff options
author | Yorick Peterse <yorickpeterse@gmail.com> | 2019-02-06 17:23:16 +0300 |
---|---|---|
committer | Yorick Peterse <yorickpeterse@gmail.com> | 2019-02-06 17:23:16 +0300 |
commit | fd838d805d8ddb0803286ac99265a9411a087ed7 (patch) | |
tree | 3b5da9a81dafcba5d63acfacb255a6f5dbf10049 | |
parent | 38b8775b56ca0175fdbe5162840bf2395cd27073 (diff) |
Document adding source installation steps
This adds a small line to the MR workflow to clarify that new source
installation requirements have to be added when they are introduced,
instead of release managers having to add them.
-rw-r--r-- | doc/development/contributing/merge_request_workflow.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/development/contributing/merge_request_workflow.md b/doc/development/contributing/merge_request_workflow.md index 9bef0635e3f..19b6181c9a2 100644 --- a/doc/development/contributing/merge_request_workflow.md +++ b/doc/development/contributing/merge_request_workflow.md @@ -86,6 +86,9 @@ request is as follows: guidelines](../merge_request_performance_guidelines.md). 1. For tests that use Capybara or PhantomJS, see this [article on how to write reliable asynchronous tests](https://robots.thoughtbot.com/write-reliable-asynchronous-integration-tests-with-capybara). +1. If your merge request introduces changes that require additional steps when + installing GitLab from source, add them to `doc/install/installation.md` in + the same merge request. Please keep the change in a single MR **as small as possible**. If you want to contribute a large feature think very hard what the minimum viable change is. |