Lines Matching +full:docs +full:- +full:review

6 Alternatively, use [GitLab's web interface](https://docs.gitlab.com/ee/user/project/merge_requests/…
8 - The default **target** branch is `main`; if your branch started from `release`, select that as th…
9 - If the merge request resolves an outstanding [issue](https://gitlab.com/petsc/petsc/issues),
10 …include a [closing pattern](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#de…
11 …cription to automatically have the issue closed when the MR is merged [^closing-patterns-release] .
15 - Select appropriate [labels](https://gitlab.com/petsc/petsc/-/labels) including a {any}`workflow l…
16 - Assign yourself to the MR.
17 - Select reviewers for the MR; clicking on `> Approval Rules` will list appropriate reviewers.
18 - If the branch started from `release` select the `milestone` of `Vxx.yy-release-fixes`
19 - For changes only to documentation, add the `docs-only` label, which will
22 - If appropriate, once the MR has been submitted, refresh the browser and select Pipelines to exami…
26 - Make sure the fork is public -- as GitLab merge request process does not work well with a private…
27 - Select the correct target repository `petsc/petsc` along with the target branch.
28 - Select the "Allow commits from members who can merge to the target branch" option.
29 - GitLab does not allow you to set labels, so `@`-mention one of the developers in a comment so the…
35 …d reviewing, is managed by [workflow labels](https://gitlab.com/petsc/petsc/-/labels?subscribed=&s…
39 - `workflow::Pipeline-Testing` The user is testing their branch. Generally, unless asked, no one el…
40 - `workflow::Review` The user would like their branch reviewed.
41 - `workflow::Ready-For-Merge` The MR has passed all tests, passed the review, has no outstanding th…
47 - `workflow::Request-For-Comment` The branch is not being requested to be merged, but the user woul…
48 - `workflow::In-Development` The developer is working on the branch. Other developers not involved …
51 The developer usually eventually converts these two states to `workflow::Review`.
59 Once the MR has passed the pipeline, it is ready for review.
60 …bmitter/assignee must change the {any}`workflow label <sec_workflow_labels>` to `workflow::Review`.
70 - by clicking on the left end of a specific line in the `Changes` window. A useful feature is the […
71 - or in the overview if it is a general comment. When introducing a new topic (thread) in reviewing…
81 and re-run the pipeline.
84 …iewers to the MR and request in the MR discussion these same people to review by @-mentioning them.
90 the **submitter/assignee** must set the label to {any}`workflow::Ready-For-Merge <sec_workflow_labe…
95 …osing-patterns-release]: Unfortunately, these closing patterns [only work for MRs to a single defa…