about summary refs log tree commit diff
path: root/triagebot.toml
AgeCommit message (Collapse)AuthorLines
2023-12-18Rollup merge of #119080 - onur-ozkan:comment-change-id-in-example-config, ↵Matthias Krüger-3/+3
r=Kobzol Comment out `change-id` in `config.example.toml` This way, we only update CONFIG_CHANGE_HISTORY for major changes, which is much simpler (and updating example.toml doesn't make much sense) r? `@Kobzol` (as this was mainly your idea)
2023-12-18Comment out `change-id` in `config.example.toml`onur-ozkan-3/+3
This way, we only update CONFIG_CHANGE_HISTORY for major changes, which is much simpler (and updating example.toml doesn't make much sense) Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-12-15Rollup merge of #118985 - JohnTitor:rm-jtitor-diag-pings, r=compiler-errorsMatthias Krüger-3/+3
Remove @JohnTitor from diagnostics pings I've been inactive around diagnostics for a while so would like to remove myself from the diagnostics-related ping groups for now.
2023-12-15Notify lcnr and errs when relations changeMichael Goulet-0/+8
2023-12-16Remove @JohnTitor from diagnostics pingsYuki Okushi-3/+3
I've been inactive around diagnostics for a while so would like to remove myself from the diagnostics-related ping groups for now.
2023-12-11Wesley is not on vacationWesley Wiser-1/+1
All good things...
2023-12-11Include the new crate in triagebot pingsNadrieril-0/+4
2023-12-07Ping GuillaumeGomez for changes in rustc_codegen_gccGuillaume Gomez-1/+1
2023-11-30Wesley is on vacationWesley Wiser-1/+1
2023-11-27Rollup merge of #114708 - tgross35:tgross35-patch-1, r=Mark-SimulacrumMichael Goulet-0/+1
Allow setting `rla` labels via `rustbot` https://github.com/rust-lang/rust-log-analyzer/pull/75 adds a `rla-silenced` label flag that will turn off RLA updates for non-bors tests. Allow setting that labels and others via `rustbot`.
2023-11-26Remove myself from users on vacationWaffle Maybe-1/+1
2023-11-25Rollup merge of #118255 - dtolnay:mentionsrustanalyzer, r=Mark-SimulacrumLeón Orell Valerian Liehr-0/+6
Request that rust-analyzer changes are sent upstream first if possible This automates `@lnicola's` comment https://github.com/rust-lang/rust/pull/118253#issuecomment-1825925242. Rustbot will write a comment similar to https://github.com/rust-lang/rust/pull/116743#issuecomment-1763178813.
2023-11-24move CONFIG_CHANGE_HISTORY to its own moduleonur-ozkan-3/+15
Because bootstrap lib is already large and complicated, this should make the "bumping change-id" process easier. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-11-24Request that rust-analyzer changes are sent upstream first if possibleDavid Tolnay-0/+6
2023-11-17Add stable mir members to triagebot configCelina G. Val-0/+9
2023-11-08accept review suggestionTshepang Mbambo-1/+1
Co-authored-by: joboet <jonasboettiger@icloud.com>
2023-11-08triagebot.toml: use inclusive languageTshepang Mbambo-1/+1
2023-11-05Remove from vacation and compiler review groupJack Huey-3/+2
2023-11-03triagebot no-merges: exclude different casePeter Jaszkowiak-1/+1
"Subtree update" as well
2023-11-02oli.pause()Michael Goulet-1/+1
2023-10-26Rollup merge of #117202 - TaKO8Ki:revert-remove-TaKO8Ki-from-reviewers, ↵Matthias Krüger-0/+2
r=Nilstrieb Revert "Remove TaKO8Ki from reviewers" ref #116061 It's been a month since this pull request, and I now have some available time for reviews. Would it be okay to revisit it as a reviewer? This reverts commit 8e06b25e3900b8b14d9043ff6d2b846199672b2b. r? `@Nilstrieb`
2023-10-26Revert "Remove TaKO8Ki from reviewers"Takayuki Maeda-0/+2
This reverts commit 8e06b25e3900b8b14d9043ff6d2b846199672b2b.
2023-10-23Remove smir from triage and add me to stablemirOğuz Ağcayazı-5/+1
2023-10-19trigger the triagebot for modifications to bootstrap/defaultsonur-ozkan-0/+2
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-19fix bootstrap paths in triagebot.tomlonur-ozkan-8/+8
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-16Rollup merge of #116808 - ouz-a:add_myself_to_triage, r=NilstriebGuillaume Gomez-1/+1
Add myself to smir triage I would like get pinged when someone makes changes to smir
2023-10-16add myself to smir triageOğuz Ağcayazı-1/+1
2023-10-16Rollup merge of #114157 - pitaj:triagebot_no-merges, r=ehussMatthias Krüger-0/+4
Enable triagebot no-merges check Follow-up on https://github.com/rust-lang/triagebot/pull/1704 ### Motivation Occasionally, a merge commit like https://github.com/rust-lang/rust/commit/cb5c011670ce8d073d0aae8c45e73c20593bfa11 makes it past manual review and gets merged into master. At one point, we tried adding a check to CI to prevent this from happening (https://github.com/rust-lang/rust/pull/105058), but that ended up [problematic](https://github.com/rust-lang/rust/pull/106319#issuecomment-1368144076) and was [reverted](https://github.com/rust-lang/rust/pull/106320). This kind of check is simply too fragile for CI, and there must be a way for a human to override the bot's decision. The capability to detect and warn about merge commits has been present in triagebot for quite some time, but was never enabled at rust-lang/rust, possibly due to concerns about false positives on rollup and subtree sync PRs. This PR intends to alleviate those concerns. ### Configuration This configuration will exclude rollup PRs and subtree sync PRs from merge commit detection, and it will post the default warning message and add the `has-merge-commits` and `S-waiting-on-author` labels when merge commits are detected on other PRs. The eventual vision is to have bors refuse to merge if the `has-merge-commits` label is present. A reviewer can still force the merge by removing that label if they so wish. ### Note for contributors The rollup tool should add that label automatically, but anyone performing subtree updates should begin including "subtree update" in the titles of those PRs, to avoid false positives. r? infra ## Open Questions 1. This configuration uses the default message that's built into triagebot: > There are merge commits (commits with multiple parents) in your changes. We have a [no merge policy](https://rustc-dev-guide.rust-lang.org/git.html#no-merge-policy) so these commits will need to be removed for this pull request to be merged. > > You can start a rebase with the following commands: > ```shell-session > $ # rebase > $ git rebase -i master > $ # delete any merge commits in the editor that appears > $ git push --force-with-lease > ``` Any changes to this are easy, I'll just have to add a `message` option. Should we mention the excluded titles in the message?
2023-10-16Rollup merge of #116776 - WaffleLapkin:hell-yeah-review-requested, ↵Matthias Krüger-0/+6
r=Mark-Simulacrum Enable `review-requested` feature for rustbot See https://github.com/rust-lang/triagebot/pull/1733. r? `@Mark-Simulacrum`
2023-10-15Enable triagebot no-merges checkPeter Jaszkowiak-0/+4
This configuration will exclude rollup PRs and subtree sync PRs from merge commit detection. On other PRs, it will post the default warning message and add the `has-merge-commits` and `S-waiting-on-author` labels when merge commits are detected. The eventual vision is to have bors refuse to merge if the `has-merge-commits` label is present. A reviewer can still force the merge by removing that label if they so wish.
2023-10-16Enable `review-requested` feature for rustbotWaffle Maybe-0/+6
2023-10-15Rollup merge of #116755 - scottmcm:review-rotation, r=Mark-SimulacrumMatthias Krüger-1/+1
Remove me from libcore review rotation I'm looking at my commitments right now, and unfortunately this needs to go for at least a while. If there's something in particular I can probably still take them, but I should drop out of the rotation for now.
2023-10-15Remove me from libcore review rotationScott McMurray-1/+1
2023-10-14Rollup merge of #116661 - WaffleLapkin:make-reviews-change-pr-state, ↵Guillaume Gomez-0/+6
r=Mark-Simulacrum Make "request changes" reviews apply `S-waiting-on-author` This makes it so **assignee** requesting changes on a PR via GitHub UI adds https://github.com/rust-lang/rust/labels/S-waiting-on-author and removes https://github.com/rust-lang/rust/labels/S-waiting-on-review. cc `@compiler-errors` :3
2023-10-12Make "request changes" reviews apply `S-waiting-on-author`Waffle Maybe-0/+6
2023-10-03Mark myself as vacation or whateverWaffle Maybe-1/+1
2023-10-02Auto merge of #115898 - onur-ozkan:config-change-tracking, r=Mark-Simulacrumbors-0/+5
bootstrap major change detection implementation The use of `changelog-seen` and `bootstrap/CHANGELOG.md` has not been functional in any way for many years. We often do major/breaking changes but never update the changelog file or the `changelog-seen`. This is an alternative method for tracking major or breaking changes and informing developers when such changes occur. Example output when bootstrap detects a major change: ![image](https://github.com/rust-lang/rust/assets/39852038/ee802dfa-a02b-488b-a433-f853ce079b8a)
2023-10-01add triagebot notification for bootstrap config changesonur-ozkan-0/+5
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-09-25Split out the stable part of smir into its own crate to prevent accidental ↵Oli Scherer-0/+4
usage of forever unstable things
2023-09-22Remove TaKO8Ki from reviewersNilstrieb-2/+0
2023-09-20Allow anyone to set llvm-fixed-upstreamNikita Popov-1/+1
Allow llvm-* to be set by unauthenticated users, which is currently llvm-main and llvm-fixed-upstream.
2023-09-18Expand infra-ci reviewer listMark Rousskov-0/+1
2023-09-17Add me as on vacationJack Huey-1/+1
2023-09-13Remove `clubby789` from `users_on_vacation`clubby789-1/+1
2023-09-11Remove spastorino as "on vacation"Santiago Pastorino-1/+1
2023-09-05Auto merge of #115342 - GuillaumeGomez:fmease-rotations, r=rustdocbors-0/+1
Add `fmease` to rustdoc review rotations `@fmease` asked me if it was okay for them to be part of the rustdoc review rotation. Since they are already reviewing a lot of rustdoc PRs, I think it's fine to add them to the rotation. What do you think `@rust-lang/rustdoc` ? r? rust-lang/rustdoc
2023-09-01Add spastorino on vacationSantiago Pastorino-1/+1
2023-08-29Add `fmease` to rustdoc review rotationsGuillaume Gomez-0/+1
2023-08-28Devacationize oli-obkOli Scherer-1/+1
2023-08-27replace outdated github username 'ozkanonur'ozkanonur-2/+2
Signed-off-by: ozkanonur <work@onurozkan.dev>
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 06:38:54 +0000