New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
github-automation: Use the llvm/llvm-project repo for backport pull requests #71727
Conversation
…equests Now that the project uses PRs for code review, we don't need to use the llvm/llvm-project-release-prs repo for reviewing backports.
✅ With the latest revision this PR passed the Python code formatter. |
Do we want to merge this now? or just wait until 17.x is done? otherwise I'll have PRs in two different repos that I need to check. |
@tru We should wait until 17.x is done to merge this. |
@tru This is ready for review/merge now. |
Hmm. Yeah - I wonder if we should allow for a little more time to make sure we don't want to do an emergency 17.x release. I guess we still could but we would have to ad-hoc the cherry-picking in that case. I guess I am fine with that as well, we just need to keep that in mind. |
Ok, it's fine with me too if we want to wait a little longer. |
@tru Ping on this one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…equests (llvm#71727) Now that the project uses PRs for code review, we don't need to use the llvm/llvm-project-release-prs repo for reviewing backports.
Now that the project uses PRs for code review, we don't need to use the llvm/llvm-project-release-prs repo for reviewing backports.