Bitbucket merge API doesn't always include an id in the response
Closed this issue · 0 comments
fgrutsch commented
It seems like that the bitbucket merge API endpoint is not always including the id field in the response and therefore deserialization can fail.
We can ignore the response body parsing as it's not needed and can only check the HTTP status for success/failure.