fix: removed unnecessary guard for no blocking labels #25
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.
I added a guard to check if the blocking labels were empty. It defaults to an empty string which
jq
can handle converting to an empty array, so the guard is unnecessary and actually breaks the action if no blocking labels are specified.I've removed the guard and you can see it working as intended when no blocking labels are specified.
See these two test issues when there are no blocking labels: