You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a situation where some PRs will be linked to JIRA issues and some won't, which I imagine is fairly common.
However because the find-issue-key errors when the input doesn't have a JIRA issue (at least when using the string input mode) my whole workflow fails.
Ideally the output is just set to '', this could be via a new parameter like optional: true to not effect any current users who rely on the failure.
Also are these actions maintained anymore? I'd like to keep using the "verified as Atlassian" actions but there doesn't seem to have been anything done since late 2020.
The text was updated successfully, but these errors were encountered:
Hi,
I've got a situation where some PRs will be linked to JIRA issues and some won't, which I imagine is fairly common.
However because the find-issue-key errors when the input doesn't have a JIRA issue (at least when using the
string
input mode) my whole workflow fails.Ideally the output is just set to
''
, this could be via a new parameter likeoptional: true
to not effect any current users who rely on the failure.Also are these actions maintained anymore? I'd like to keep using the "verified as Atlassian" actions but there doesn't seem to have been anything done since late 2020.
The text was updated successfully, but these errors were encountered: