Skip to content

Migrate from highfive to triagebot #9963

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

Merged
merged 1 commit into from
Nov 27, 2022
Merged

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Nov 26, 2022

This migrates this repository from using the highfive bot to using triagebot (aka rustbot).

This should not be merged without coordinating the removal of the highfive webhook and/or merging rust-lang/highfive#435.

changelog: none

@rust-highfive
Copy link

r? @Jarcho

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties label Nov 26, 2022
@Jarcho
Copy link
Contributor

Jarcho commented Nov 26, 2022

r? @flip1995

@rust-highfive rust-highfive assigned flip1995 and unassigned Jarcho Nov 26, 2022
@xFrednet
Copy link
Member

I'd be interested in the context of this change. Is the goal to deprecate rust-highfive? Having the config in this repo will make it easier for us to have control, so I can definitely see and advantage in this :)

@ehuss ehuss changed the title Migrate from highfive to triagebot [DO NOT MERGE] Migrate from highfive to triagebot Nov 27, 2022
@ehuss
Copy link
Contributor Author

ehuss commented Nov 27, 2022

Yes, we are removing highfive.

BTW, just to be clear, please do not merge this. This requires infra to be involved.

@xFrednet xFrednet marked this pull request as draft November 27, 2022 14:39
@xFrednet
Copy link
Member

Interesting, We'll miss you @rust-highfive <3

I've marked the PR as a draft, to ensure that it won't get merged :)

@ehuss ehuss force-pushed the highfive-triagebot branch from 1c81fa6 to 13dfbb2 Compare November 27, 2022 15:24
@ehuss ehuss changed the title [DO NOT MERGE] Migrate from highfive to triagebot Migrate from highfive to triagebot Nov 27, 2022
@ehuss ehuss marked this pull request as ready for review November 27, 2022 15:48
@ehuss
Copy link
Contributor Author

ehuss commented Nov 27, 2022

This should be ready to go.

# Allows shortcuts like `@rustbot ready`
#
# See https://github.com/rust-lang/triagebot/wiki/Shortcuts
[shortcut]

[assign]
contributing_url = "https://github.com/rust-lang/rust-clippy/blob/master/CONTRIBUTING.md"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this field do? Like where is it mentioned? :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the welcome message to new users. It looks like this. There is documentation for the assignment options at https://github.com/rust-lang/triagebot/wiki/Assignment#additional-new-pr-trigger-options.

@xFrednet
Copy link
Member

Alright, thank you. Then this looks good to me, let's see if everything works smoothly. I'll monitor new incoming PRs to ensure that someone gets assigned to each of them. Thank you for the help!

@bors r+

@bors
Copy link
Contributor

bors commented Nov 27, 2022

📌 Commit 13dfbb2 has been approved by xFrednet

It is now in the queue for this repository.

bors added a commit that referenced this pull request Nov 27, 2022
Migrate from highfive to triagebot

This migrates this repository from using the highfive bot to using triagebot (aka rustbot).

This should not be merged without coordinating the removal of the highfive webhook and/or merging rust-lang/highfive#435.
@bors
Copy link
Contributor

bors commented Nov 27, 2022

⌛ Testing commit 13dfbb2 with merge 4664959...

@bors
Copy link
Contributor

bors commented Nov 27, 2022

💔 Test failed - checks-action_test

@xFrednet
Copy link
Member

@bors retry

@bors
Copy link
Contributor

bors commented Nov 27, 2022

⌛ Testing commit 13dfbb2 with merge ef84397...

@bors
Copy link
Contributor

bors commented Nov 27, 2022

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: xFrednet
Pushing ef84397 to master...

@bors bors merged commit ef84397 into rust-lang:master Nov 27, 2022
@xFrednet
Copy link
Member

Hey @ehuss, after this PR new PRs have stopped receiving the S-waiting-on-review label.

You included these lines in a previous version, but removed them again:

[autolabel."S-waiting-on-review"]
new_pr = true

Was there a reason for this change and would it be enough to add to the config file?

@ehuss
Copy link
Contributor Author

ehuss commented Nov 29, 2022

Oh, yea, sure! Sorry about that, I posted #9985 to add it. I was looking at the homu config and noticed clippy wasn't using autolabels and for some reason didn't think it was being used here.

bors added a commit that referenced this pull request Nov 29, 2022
Add S-waiting-on-review autolabel.

This adds the S-waiting-on-review autolabel feature for new PRs.  This was previously handled by highfive, but I neglected to include it in #9963.

changelog: none
@xFrednet
Copy link
Member

No problem, thank you for adding it again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants