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
{{ message }}
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
I was recently confused by the bors UI while trying to introduce a blocking condition using the pr_status field in bors.toml. Even though the logic was working correctly, and merging was in fact blocked because of the PR check, the PR was listed as "Mergeable" in the bors web UI. See picture:
I couldn't tell the pr_status check was working without actually trying to do bors r+, which correctly refused the merge.
Would it make sense to have the "Mergeable" column in the web UI reflect the status of pr_status checks? Alternatively, adding this information in a new column?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was recently confused by the bors UI while trying to introduce a blocking condition using the
pr_status
field inbors.toml
. Even though the logic was working correctly, and merging was in fact blocked because of the PR check, the PR was listed as "Mergeable" in the bors web UI. See picture:I couldn't tell the
pr_status
check was working without actually trying to dobors r+
, which correctly refused the merge.Would it make sense to have the "Mergeable" column in the web UI reflect the status of
pr_status
checks? Alternatively, adding this information in a new column?The text was updated successfully, but these errors were encountered: