Document `object_attributes.oldrev` in the merge request webhook event
What does this MR do and why?
Adds to the documentation to describe when is the object_attributes.oldrev
field available.
This field is not always present in the webhook body so it's good to know when it will appear.
Screenshots or screen recordings
None
How to set up and validate locally
This is just a documentation change so it should be enough to read the changed text.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
Hey @spotlesstofu!
Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.
When you're ready for a first review, post
@gitlab-bot ready
. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with@gitlab-bot ready @user1 @user2
.At any time, if you need help moving the MR forward, feel free to post
@gitlab-bot help
. Read more on how to get help.To enable automated checks on your MR, please configure Danger for your fork.
You can comment
@gitlab-bot label <label1> <label2>
to add labels to your MR. Please see the list of allowed labels in thelabel
command documentation.This message was generated automatically. You're welcome to improve it.
added Community contribution workflowin dev labels
assigned to @spotlesstofu
@gitlab-bot ready
added workflowready for review label and removed workflowin dev label
Hi @kpaizee! Please review this documentation merge request.
added documentation twtriaged labels
- Resolved by Kati Paizee
@justin_ho, could you please review this Community contribution or assign other reviewer(s) if you do not have availability or domain expertise?
Please add the workflowin dev label if the merge request needs actions from the author.
requested review from @justin_ho
added 1st contribution label
added ~24308234 groupintegrations [DEPRECATED] + 1 deleted label
requested review from @.luke and removed review request for @justin_ho
- Resolved by Kati Paizee
Thank you @spotlesstofu for this contribution!
I'll assign this to our Technical Writer for a review!
@kpaizee Could you please give this Community contribution its documentation review? Thank you!
changed milestone to %15.2
Suggested Reviewers (beta)
The individuals below may be good candidates to participate in the review based on various factors.
You can use slash commands in comments to quickly assign
/assign_reviewer @user1
.Suggested Reviewers @marcel.amirault
,@aqualls
,@axil
,@toupeira
,@sselhorn
If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/357923
.Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
doc/user/project/integrations/webhook_events.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Generated by
Dangermentioned in issue gitlab-org/quality/triage-reports#8151 (closed)
added Technical Writing docsimprovement twdoing typemaintenance labels and removed twtriaged label
- Resolved by Camilla Conte
- Resolved by Camilla Conte
- Resolved by Camilla Conte
enabled an automatic merge when the pipeline for 3a5a5774 succeeds
@spotlesstofu, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:
- Leave a
or a on this comment to describe your experience. - Create a new comment starting with
@gitlab-bot feedback
below, and leave any additional feedback you have for us in the comment.
Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.
Thanks for your help!
- Leave a
mentioned in commit 0170277d
added workflowstaging-canary label and removed workflowready for review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added devopsmanage label and removed 1 deleted label
added groupimport and integrate label and removed groupintegrations [DEPRECATED] label