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
When the action does a release it by default tries to comment on the linked issues of each PR included in the release, mentioning in which release the issue was addressed.
We came across a case whereby the linked issue was in a different repo, which failed the action. See here.
The action needs to handle this more correctly and post the comment on the issue in a "best effort" way. It should still try, but it shouldn't fail the execution if it cannot comment. Also note that I'm not even sure this case should have failed, it's just that the action tried to post the comment on an issue that doesn't exist because it was searching for that issue in the same repo, whereas it was an external repo.
The text was updated successfully, but these errors were encountered:
When the action does a release it by default tries to comment on the linked issues of each PR included in the release, mentioning in which release the issue was addressed.
We came across a case whereby the linked issue was in a different repo, which failed the action. See here.
The action needs to handle this more correctly and post the comment on the issue in a "best effort" way. It should still try, but it shouldn't fail the execution if it cannot comment. Also note that I'm not even sure this case should have failed, it's just that the action tried to post the comment on an issue that doesn't exist because it was searching for that issue in the same repo, whereas it was an external repo.
The text was updated successfully, but these errors were encountered: