[petsc-dev] clarification of merge request labels and process

Barry Smith bsmith at petsc.dev
Wed Jul 1 20:57:40 CDT 2020


   The information for what each workflow: label means is given at https://gitlab.com/petsc/petsc/-/labels <https://gitlab.com/petsc/petsc/-/labels>

    If everyone sets the labels correctly the merging will go easy and require less sending email or extra prompts to specific people.

    In particular always use

        workflow:Ready-To-Merge when the pipeline passes, all the threads are resolved and the MR has sufficient approvals.  Then you don't have to bug anyone to move the MR along

       workflow:Review for when you want people to review and comment on or approve your MR (often when you open the MR)

       Set appropriate Assignees, you will get prompter reviews.  Click on View eligible approvers, this will indicate who needs to approve you MR based on what you changed. List appropriate people from this list in Assignees.

  
   Thanks

    Barry

  Note: by setting Gitlab notification options and appropriate mail filters it should be possible to direct Gitlab mail into separate mail-boxes for quicker processing. For example I filter pipeline messages into a pipeline mail box, issue messages into an issue mailbox, you might be able to filter assignment of MR to a separate mail box.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20200701/1f2fadfb/attachment.html>


More information about the petsc-dev mailing list