Does the gitlab merge request approval rule allow me to set the user specify a mandatory field (for example a mandatory comment), or just who can approve the merge requests?
Related
We have created two user groups to accept merges request.
The group "Testing" and "Code review".
Some users are in both groups.
Our merges request need two approvals to be merged.
We would like a user who is in the "Testing" group and in the "Code review" group to be able to validate the merge request twice. Once as a "receiver" and once as a "code review".
How to make the same person give his approval twice?
It doesn't seem possible.
Thanks for your help,
Have a nice day,
I was going through gitlab docs for webhooks but did not find how to setup the URL/endpoint.
If there are no pre-defined URLs then I have to create / manage URLs/endpoint, it is overhead because I have to manage the infrastructure and the write the code as well to create the endpoints .
So, are there any pre-defined webhooks ? , if yes , how to get that ?
further, my exact requirement is, whenever, merge request gets merged, I have to update one of the gitlab pipeline job to proceed further. is that possible through webhooks and event API ? if yes, any documentation for that please ? I see that webhook receiver is there but not sure if that will solve my requirement.
please suggest
The URL/endpoints configured in webhooks are designed to be received by external applications, either made by you or third parties. As stated in the docs:
Usually, you set up your own webhook receiver to receive information from GitLab and send it to another app, according to your requirements.
In other words, GitLab itself has no endpoints you can point to that will respond to a webhook you configure on the repo, aside from the few builtin receivers, like for slack notifications which are configured through integrations.
whenever, merge request gets merged, I have to update one of the gitlab pipeline job to proceed further. is that possible through webhooks and event API ?
Yes it's possible, but in order to get the effect you want, you'll have to implement the HTTP service endpoint to receive the webhook yourself.
We are using Azure DevOps. 'Minimum number of reviewers' is set to 1, 'Allow requestors to approve their own changes' is enabled in branch specific policy and 'Prohibit the most recent pusher from approving their own changes' is checked in 'Cross-Repository policies for master'.
The issue we face is that, if a developer who is also a reviewer create a pull request, he cannot approve his own pull request and needs to wait for a review. Is it possible to give permission for reviewers to accept their own changes?
Even if I am against approving your own PR, you can enable it by
Branch Policies --> Allow requestors to approve their own changes
This appears to be a bug in DevOps when "When new changes are pushed: Require at least one approval on the last iteration" is checked. If you change that setting to "When new changes are pushed: Reset all approval votes ..." then it will allow them to approve their own request."
What's the difference between the content approval functionality and the workflow functionality in SharePoint. Can someone help me list some pros and cons too?
Approval workflow can specify multiple users in a certain order to approve the item.
If any participant rejects the document, the approval workflow can choose to automatically reject the document.
If changes are made before the workflow is completed, approval workflow automatically rejects the document.
Approval workflow could update the approval status after the workflow is completed.
Similar issue for your reference:
https://sharepoint.stackexchange.com/questions/116290/difference-between-content-approval-and-document-approval-workflow#:~:text=Document%20Approval%20Workflows%20are%20created,a%20custom%20SharePoint%20Designer%20Workflow.&text=In%20simple%20terms%2C%20when%20Content,to%20others%20until%20it's%20published.
https://social.technet.microsoft.com/Forums/en-US/c8cd11c3-9a80-4b1a-a406-54634bfdbcd5/approval-workflow-vs-content-approval-feature-on-listlibrary?forum=sharepointgeneralprevious
I am using SOAP API and I want my recipient to sign without any routing order, meaning whoever access first gets to sign first.
Is this possible?
I changed my routing order to all 1. It prompts me to add the signature tab.
FYI, I am creating a signature tab not via templates ( I have configured the same roles with my templates) as I am using one form to generate multiple signatures and it is working. I just need to make the routing order to be disabled.
A routing order must be specified in the DocuSign workflow prior to sending out the envelope. From what you describe though, I would recommend looking into the new Signing Groups feature: https://www.docusign.com/supportdocs/cdse-user-guide/Content/advanced-sending/using-signing-groups.htm.