Skip to content

webhooks: include old revision in MR update events

What does this MR do?

Includes the old revision for an MR in webhooks.

Are there points in the code the reviewer needs to double check?

The docs do not give an example update hook; should I add one?

Why was this MR needed?

In order to keep web hook listeners stateless, it helps to include the previous revision of the MR in the hook so that it does not need to remember the last revision (which may also be wrong in case of missed or out-of-order events due to previous errors).

What are the relevant issue numbers?

N/A

Screenshots (if relevant)

N/A

Does this MR meet the acceptance criteria?

Merge request reports