We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The conflict notification tries to determine which PR caused the conflict. However, with merge queues, it seems to be failing to do this:
rust-lang/reference#1664 (comment) is an example. It should be able to see that rust-lang/reference@06994b6 is rust-lang/reference#1696.
The code for this is here:
triagebot/src/handlers/merge_conflicts.rs
Lines 169 to 179 in 0400514
I'm wondering if there is a race on the GitHub side, where it computes this information async, and the information is not yet available?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The conflict notification tries to determine which PR caused the conflict. However, with merge queues, it seems to be failing to do this:
rust-lang/reference#1664 (comment) is an example.
It should be able to see that rust-lang/reference@06994b6 is rust-lang/reference#1696.
The code for this is here:
triagebot/src/handlers/merge_conflicts.rs
Lines 169 to 179 in 0400514
I'm wondering if there is a race on the GitHub side, where it computes this information async, and the information is not yet available?
The text was updated successfully, but these errors were encountered: