Skip to content
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

Do not ping PR reviewers in toolstate breakage #69449

Merged
merged 1 commit into from
Feb 28, 2020

Conversation

JohnTitor
Copy link
Member

@JohnTitor JohnTitor commented Feb 25, 2020

As per #69419 (comment)

We should also remove author part?

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 25, 2020
@Mark-Simulacrum
Copy link
Member

I think pinging the PR author is at least reasonable, though I agree that many PR authors in practice won't followup (and leave it to tool people). I think that mostly speaks to a not-great experience to the "I want to fix tools" story today, though.

I'd like T-compiler sign-off on this as the primary affected party, though I think FCP is overkill -- let's just see if anyone objects at/before the meeting. cc @rust-lang/compiler

@Mark-Simulacrum Mark-Simulacrum added I-nominated T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 25, 2020
@nikomatsakis
Copy link
Contributor

I think it's ok either way

@pnkfelix
Copy link
Member

discussed at T-compiler meeting. All were in favor of this change. Some were in favor of going further (e.g. removing PR author as well) but we opted to leave that discussion for a later point. I.e. lets not block this PR on that question.

@Mark-Simulacrum
Copy link
Member

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Feb 27, 2020

📌 Commit 8d0e918 has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 27, 2020
Dylan-DPC-zz pushed a commit to Dylan-DPC-zz/rust that referenced this pull request Feb 27, 2020
…mulacrum

Do not ping PR reviewers in toolstate breakage

As per rust-lang#69419 (comment)

We should also remove author part?
bors added a commit that referenced this pull request Feb 27, 2020
Rollup of 8 pull requests

Successful merges:

 - #60826 (Implement new gdb/lldb pretty-printers)
 - #69255 (Add more context to E0599 errors)
 - #69379 (Fail on multiple declarations of `main`.)
 - #69430 (librustc_typeck: remove loop that never actually loops)
 - #69449 (Do not ping PR reviewers in toolstate breakage)
 - #69491 (rustc_span: Add `Symbol::to_ident_string` for use in diagnostic messages)
 - #69495 (don't take redundant references to operands)
 - #69496 (use find(x) instead of filter(x).next())

Failed merges:

r? @ghost
bors added a commit that referenced this pull request Feb 28, 2020
Rollup of 9 pull requests

Successful merges:

 - #69379 (Fail on multiple declarations of `main`.)
 - #69430 (librustc_typeck: remove loop that never actually loops)
 - #69449 (Do not ping PR reviewers in toolstate breakage)
 - #69491 (rustc_span: Add `Symbol::to_ident_string` for use in diagnostic messages)
 - #69495 (don't take redundant references to operands)
 - #69496 (use find(x) instead of filter(x).next())
 - #69501 (note that find(f) is equivalent to filter(f).next() in the docs.)
 - #69527 (Ignore untracked paths when running `rustfmt` on repository.)
 - #69529 (don't use .into() to convert types into identical types.)

Failed merges:

r? @ghost
@bors bors merged commit ab45408 into rust-lang:master Feb 28, 2020
@JohnTitor JohnTitor deleted the toolstate-ping branch February 28, 2020 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants