Commit 2588c298 authored by Utkarsh Ayachit's avatar Utkarsh Ayachit
Browse files

Update docs to reflect change in merge policy.

parent eb32c260
Pipeline #15751 passed with stage
......@@ -351,12 +351,10 @@ convention, do not request a merge if any `-1` or `Rejected-by:`
review comments have not been resolved and superseded by at least
`+1` or `Acked-by:` review comments from the same user.
Caveats:
* Currently, developers authorized to do a merge request will be limited to those
who have **Master** privileges on the ParaView Gitlab repository. This preserves the
spirit of **Gatekeeper Review** in the previous development workflow. This decision
may be reevaluated in the future and lifted to encourage a more open development
community.
Developers are encouraged to merge their own merge requests on review. However,
please do not merge unless you are available to address any dashboard issues that may
arise. Developers who repeatedly ignore dashboard issues following their merges may
loose developer privileges to the repository temporarily (or permanently)!
### Merge Success ###
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment