Closed maelvls closed 11 months ago
@maelvls: Overrode contexts on behalf of maelvls: dco
/override dco
@maelvls: Overrode contexts on behalf of maelvls: dco
Name | Link |
---|---|
Latest commit | 550f1f160c6894379e6dbf5a2afe49ba6be268b7 |
Latest deploy log | https://app.netlify.com/sites/cert-manager-website/deploys/6571ad3a34ddd80008a63190 |
Deploy Preview | https://deploy-preview-1357--cert-manager-website.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/approve /lgtm
@inteon: adding LGTM is restricted to approvers and reviewers in OWNERS files.
Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:
@mael can you force push the master branch to release-next instead? That will prevent a merge commit from being created.
/override dco
@maelvls: Overrode contexts on behalf of maelvls: dco
We decided to let the person click "Merge" in the UI instead of waiting for someone to approve to avoid having to ask another person to do this task. See decision in Slack.
To be added to the contributor documentation:
If you find that the release-next
branch is missing some changes from master
and are a GitHub admin of the website repository, you can click "Merge" in the UI instead of waiting for someone to approve to avoid having to ask another person to do this task.
/approve
Can someone LGTM? 😅
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: inteon, maelvls
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
@inteon: adding LGTM is restricted to approvers and reviewers in OWNERS files.
~/hold~
~I want to hold Prow from auto-merging this PR we prefer not having needless merge commits when master
can be fast-forwarded to release-next
.~
Richard agreed that we don't need another dev interaction for merging this kind of PR. I will click "Merge" manually.
Tanuj needs the release-next branch to be up to date so that he knows where to put the documentation about
nameConstraints
./hold
I want to hold Prow from auto-merging this PR we prefer not having needless merge commits when
master
can be fast-forwarded torelease-next
. Once this PR gets approved, I run the following commands:/override dco
I used the command
/override dco
is necessary because some the merge commits have been written by the bot and do not have a DCO signoff. The command/override dco
needs to be re-issued every time a commit is merged tomaster
.