fix(github): Resolve branch name issue for protected branches #1415
+32
−4
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.
Summary:
Resolves #1417
Currently it's not possible to perform any api action on protected branches using the Github integration. The branch name is not determined correctly as the logic assumes the
branchto be a simple string when it's actually an object.Description for the changelog:
Check if the branch parameter is an object to access the
valuefield for the branch name, otherwise use the parameter as thebranchname.Declaration:
Other info:
❌