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
There are 3 types of comments that can be made related to a pull request:
Issue comments, which – despite their name – are comments made directly in the pull request. Most of our @bors commands are made here.
Review comments, which are comments made on the code diff of a merge request
Commit comments, which are comments made on the commit itself (and we do not support in @bors).
I wrote a script to go through all of our pull requests to quantify how many bors commands appear in review comments. Here are the results:
Repo
Review comment commands
rust-lang/cargo
0
rust-lang/rust-clippy
0
rust-lang-nursery/compiler-builtins
0
rust-lang-nursery/crater
0
rust-lang/hashbrown
0
rust-lang/libc
0
rust-lang/regex
0
rust-lang/rls
0
rust-lang/rust
1
rust-lang/rustlings
0
rust-lang/rustup.rs
0
So, the only time this feature has been used (that I can find; I won't rule out that my code was not 100% perfect) was this 5 Dec 2018 comment.
In the spirit that the easiest code to maintain is no code, I propose that we remove support for this rarely used feature. The total cost of supporting it is pretty low, but the utility of this function appears even lower (one use in 5 years).
I believe it would mostly come down to removing the following two parts of the code:
I'm somewhat ambivalent on this. It's certainly a simplification, but it also seems somewhat odd to not support review comments as from a GH UI perspective they're quite similar. I honestly didn't think we supported them and seem to recall instances where I didn't use them as a result, so I think the statistics may be flawed in that regard.
There are 3 types of comments that can be made related to a pull request:
@bors
commands are made here.@bors
).I wrote a script to go through all of our pull requests to quantify how many bors commands appear in review comments. Here are the results:
So, the only time this feature has been used (that I can find; I won't rule out that my code was not 100% perfect) was this 5 Dec 2018 comment.
In the spirit that the easiest code to maintain is no code, I propose that we remove support for this rarely used feature. The total cost of supporting it is pretty low, but the utility of this function appears even lower (one use in 5 years).
I believe it would mostly come down to removing the following two parts of the code:
homu/homu/main.py
Lines 1507 to 1522 in df43bc0
homu/homu/server.py
Lines 372 to 402 in df43bc0
The text was updated successfully, but these errors were encountered: