Include action in webhook test payloads
What does this MR do and why?
Include action in webhook test payloads #468397 (closed).
Previously a webhook test would not include the
object_attributes.action
part of an issue, or MR, payload. This was
because it was assigned only when really executed.
This change includes the action to the webhook tests.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
- Create a project webhook:
- Choose a project, go Settings > Webhooks.
- For URL use https://webhook.site to generate a new webhook receiving URL.
- For Trigger, select Issues events and Merge requests events.
- Select Add webhook.
- Test your webhooks:
2. Go Settings > Webhooks, find your webhook and click Edit.
- Scroll down, and click Test, and choose Issues events .
- Visit your https://webhook.site URL and you should receive a webhook with an
object_attributes.action
property ("opened"
). - Note click Test, and choose Merge requests events, you should also receive a webhook with an
object_attributes.action
property ("opened"
)..
- QA that normal issue and MR webhooks are unaffected
- Go to Issues > List, and choose an issue to close.
- Visit your https://webhook.site URL and you should receive a webhook with an
object_attributes.action
property. - Go to Merge requests > List, and choose an MR to close.
- Visit your https://webhook.site URL and you should receive a webhook with an
object_attributes.action
property.
Edited by Luke Duncalfe