ID feature request, webhook trigger
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Regarding, the commit ID feature request, A c customer is using webhooks to trigger different json objects depending on the action type, like merge_request, push etc,
{
"object_kind": "merge_request",
"event_type": "merge_request",
"user": {
[...]
},
[...]
"object_attributes": {
[...]
"last_commit": {
"id": "9de82fc675e5df556e875cce8fef34da4d3bc40d",
"message": "Update Jenkinsfile",
"title": "Update Jenkinsfile",
[...]
},
}
}
{
"object_kind": "push",
"event_name": "push",
"before": "a31f0de80b7b51e4cac88a4c71743cf2fe1b2c28",
[...]
"commits": [
{
"id": "84e64401c8960aa77caba0443a7a1645b7e247d5",
"message": "xyz",
"title": "Merge branch 'branch1' into 'master'",
"timestamp": "2022-04-12T13:03:04+02:00",
[...]
},
}
}Proposal
It would be very great if we would have some common fields for all actions, in our case especially for latest commit sha like:
{
"object_kind": "merge_request",
"event_type": "merge_request",
„Last_commit_id": "84e64401c8960aa77caba0443a7a1645b7e247d5",
[...]}
{
"object_kind": "push",
"event_name": "push",
„Last_commit_id": "84e64401c8960aa77caba0443a7a1645b7e247d5",
[...]}
Reason is that we have on the other site application, witch can parse json, and get a value from field, but on which we are not able to edit source code and make any logic which would decide the proper field path depending on message type.
Intended users
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.