Skip to content

Conversation

Shunpoco
Copy link
Contributor

@Shunpoco Shunpoco commented Oct 11, 2025

Context

Discussion: https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/tidy.20isn't.20in.20.2E.2Fx.20check/with/544323712

Currently tidy (src/tools/tidy) is not included in the list of ./x check. It means that rust-analyzer doesn't work for codes in the directory if you use ./x check as the analyzer on your IDE.

Change

This PR adds src/tools/tidy into the target of ./x check. It enables rust-analyzer highlight errors/warns on all codes in the directory.

Note that since tidy is implicitly checked by ./x test tidy, this new check is off by default.

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Oct 11, 2025
@Shunpoco Shunpoco marked this pull request as ready for review October 11, 2025 21:03
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Oct 11, 2025
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Oct 11, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 11, 2025

r? @clubby789

rustbot has assigned @clubby789.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@Zalathar
Copy link
Contributor

Oh, please also add tidy to the list of tool checks in src/ci/docker/host-x86_64/pr-check-1/Dockerfile (after rustdoc-gui-test), so that x check tidy is always tested in CI.

@Zalathar
Copy link
Contributor

r? Zalathar

@rustbot rustbot assigned Zalathar and unassigned clubby789 Oct 12, 2025
This commit adds src/tools/tidy into `./x check`. It enables rust-analyzer hightlights errors/warns on all codes in src/tools/tidy.
Since tidy is implicitly checked by `./x test tidy`, this new check is off by default.
@rustbot rustbot added A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Oct 12, 2025
@Zalathar
Copy link
Contributor

Thanks!

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented Oct 12, 2025

📌 Commit d70857a has been approved by Zalathar

It is now in the queue for this repository.

@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 Oct 12, 2025
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Oct 12, 2025
…thar

Add tidy to the target of ./x check

## Context
Discussion: https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/tidy.20isn't.20in.20.2E.2Fx.20check/with/544323712

Currently `tidy` (src/tools/tidy) is not included in the list of `./x check`. It means that rust-analyzer doesn't work for codes in the directory if you use `./x check` as the analyzer on your IDE.

## Change

This PR adds src/tools/tidy into the target of `./x check`. It enables rust-analyzer highlight errors/warns on all codes in the directory.

Note that since tidy is implicitly checked by `./x test tidy`, this new check is off by default.
bors added a commit that referenced this pull request Oct 12, 2025
Rollup of 7 pull requests

Successful merges:

 - #147168 (Don't unconditionally build alloc for `no-std` targets)
 - #147178 ([DebugInfo] Improve formatting of MSVC enum struct variants)
 - #147495 (Update wasm-component-ld to 0.5.18)
 - #147576 (Fix ICE on offsetted ZST pointer)
 - #147592 (Add tidy to the target of ./x check)
 - #147597 (Add a regression test for #72207)
 - #147604 (Some clippy cleanups in compiler)

r? `@ghost`
`@rustbot` modify labels: rollup
bors added a commit that referenced this pull request Oct 12, 2025
Rollup of 6 pull requests

Successful merges:

 - #147168 (Don't unconditionally build alloc for `no-std` targets)
 - #147178 ([DebugInfo] Improve formatting of MSVC enum struct variants)
 - #147495 (Update wasm-component-ld to 0.5.18)
 - #147592 (Add tidy to the target of ./x check)
 - #147597 (Add a regression test for #72207)
 - #147604 (Some clippy cleanups in compiler)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 13ef05d into rust-lang:master Oct 12, 2025
10 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 12, 2025
rust-timer added a commit that referenced this pull request Oct 12, 2025
Rollup merge of #147592 - Shunpoco:add-tidy-to-check, r=Zalathar

Add tidy to the target of ./x check

## Context
Discussion: https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/tidy.20isn't.20in.20.2E.2Fx.20check/with/544323712

Currently `tidy` (src/tools/tidy) is not included in the list of `./x check`. It means that rust-analyzer doesn't work for codes in the directory if you use `./x check` as the analyzer on your IDE.

## Change

This PR adds src/tools/tidy into the target of `./x check`. It enables rust-analyzer highlight errors/warns on all codes in the directory.

Note that since tidy is implicitly checked by `./x test tidy`, this new check is off by default.
@Shunpoco Shunpoco deleted the add-tidy-to-check branch October 12, 2025 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants