Open evgeni opened 6 years ago
@evgeni is merge_commit_sha not equivalent to the gitlabAfter
env var?
@omehegan nope. As far as I can see, gitlabAfter
comes from the after
keyword in the push
/tag_push
hook, but not in the merge_request
hook. So while I think the hash would be the same, it is part of a different webhook (and in our setup we only look at merge_request
and note
hooks).
@evgeni ok, noted. I will look at adding this, it should be possible.
One year passed, this 'merge_commit_sha' is still not available in the environment variables. It's very impotant because it's the base key to tell the differences in a merge.
@omehegan Any update here? We could also use this as our flow currently only looks at Merge Requests. We could make the flow include pushes, but that requires extra filtering and logic, whereas this would just be nice and simple.
ok, noted. I will look at adding this, it should be possible.
@omehegan I need this feature so I'd like to implement it - could you briefly point me places where should I do it, please? It would be very helpful.
Issue
Context
Logs & Traces
None
Problem description
When merging an MR, GitLab sends the
merge_commit_sha
as part of the WebHook:It would be awesome if that would be available as part of the injected environment variables.