Feature: Add support for more fields, allow branch+commit+tag, fix error output #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds some additional parameters you can feed to the Bitrise API. These were necessary for more context in our Bitrise builds, and enabling auto-aborting of repeated builds to branches with open PRs.
I also removed the guard that requires only one of [branch|tag|commit] as params. Even though the documentation indicates you are only supposed to have one of these, the commit information still gets populated when you push a value for
-b
and-c
.This was an issue for my team, as we moved from webhooks to using Gitrise, but upon doing so and passing
-b
for the branch name, we lost commit context. This got it back for us.Also, it seems like bitrise changed the key of the error message in the response object from
message
toerror_msg
. Addressed in this MR.