Remove fork handling from release issue workflow #79310
Conversation
This is currently broken, because the check is performed on the wrong repository. repo here is llvm/llvm-project, which is not a fork (so this will always trigger), then we'll push a new branch to llvmbot/llvm-project, and then again set the wrong owner, so we'll look for the branch in llvm/llvm-project. Rather than fixing this, I'm removing the code entirely, as it shouldn't be needed anymore (llvmbot/llvm-project is a fork of llvm/llvm-project).
|
The one remaining problem now is that apparently comments posted by the github-actions bot don't trigger new actions, so the |
|
Another issue is that we get duplicate command executions if cherry-pick is part of the issue description and an issue subscriber comment gets posted. We can add |
Right, so the comment needs to be posted using one of the llvmbot tokens we have stored in the secrets. |
|
@tstellar That would work as well, but the token currently doesn't have permissions to post comments. |
This is currently broken, because the check is performed on the wrong repository. repo here is llvm/llvm-project, which is not a fork (so this will always trigger), then we'll push a new branch to llvmbot/llvm-project, and then again set the wrong owner, so we'll look for the branch in llvm/llvm-project rather than llvmbot/llvm-project.
Rather than fixing this, I'm removing the code entirely, as it shouldn't be needed anymore (llvmbot/llvm-project is a fork of llvm/llvm-project).
This will hopefully fix the failure from #79253 (comment).