about summary refs log tree commit diff
path: root/src/etc/completions
AgeCommit message (Collapse)AuthorLines
2025-08-20Add new `--test-codegen-backend` bootstrap optionGuillaume Gomez-2/+16
2025-08-13bootstrap: Update completions for new --timings argumentJosh Triplett-4/+16
2025-07-19update completionsbinarycat-24/+0
2025-07-19tidy: running of eslint, tsc, and es-check are now an extra checkbinarycat-6/+30
2025-07-15Regenerate completions after removing `./x suggest`Jieyou Xu-644/+2
2025-07-11Update description for flagbjorn3-138/+138
2025-07-11Add --compile-time-deps argument for x checkbjorn3-48/+186
This reduces the amount of time it takes to do the x check for rust-analyzer analysis from 12m16s to 3m34s when the bootstrap compiler is already downloaded.
2025-07-08tidy: add `auto:` prefix to --extra-checks syntaxbinarycat-6/+6
currently this just uses a very simple extension-based heirustic.
2025-07-04Update completionsJakub Beránek-3/+3
2025-07-03setup CI and tidy to use typos for spellchecking and fix few typosklensy-3/+3
2025-06-18Remove unused bootstrap flagJakub Beránek-646/+186
2025-06-10Rename `build` to `host_target`Jakub Beránek-138/+138
Host is the machine where bootstrap runs, and this field represents the target of the (host) stage0/beta compiler. This is much clearer than `build`, which also conflicts with the `Build` struct, which is stored under the name `build` inside `Builder` (lol).
2025-06-04update `skip_std_check_if_no_download_rustc` doc-commentsonur-ozkan-138/+138
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-06-03bless tidyonur-ozkan-48/+186
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-03-20update completion filesonur-ozkan-48/+370
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-03-17replace config.toml to bootstrap.toml in src/ci, src/etc/* and tests/run-makebit-aloo-278/+278
2025-02-05Update bootstrap completionsJakub Beránek-76/+3428
2024-12-27Add `--no-capture` as a bootstrap argumentclubby789-2/+8
2024-12-17Generate shell completions for x as wellRyan Mehri-0/+5939
2024-11-13Bump bootstrap depsclubby789-230/+230
2024-10-03bootstrap: Consolidate editor LSP setupKajetan Puchalski-1/+1
Consolidate LSP setup for different editors into one `./x setup editor`.
2024-10-01bootstrap: Add support for ./x setup vimKajetan Puchalski-1/+1
2024-10-01bootstrap: Add support for ./x setup helixKajetan Puchalski-1/+1
2024-10-01bootstrap: Add support for ./x setup emacsKajetan Puchalski-1/+1
Add support for automatically setting up the recommended LSP config for Emacs. Additionally, refactor setup.rs to make it easier to add support for more editors in the future.
2024-09-07Remove unused option from x.pyGurinder Singh-145/+19
2024-08-18Generate completions after version updatesTrevor Gross-1471/+2988
Running `cargo update` changed completion output. Regenerate them here.
2024-08-12regenerate `./x` completionsRémy Rakic-13/+6
to pick up changes to `./x miri` and `./x test` commands
2024-08-12clarify that `--rustc-args` is for compiletest testsRémy Rakic-3/+3
2024-06-27Implement `x perf` as a separate toolJakub Beránek-3/+3
2024-06-12Add `x perf` command for profiling the compiler using `rustc-perf`Jakub Beránek-1/+240
2024-05-29Remove path choice from `x fmt` and add `--all` option.Nicholas Nethercote-1/+4
By default, `x fmt` formats/checks modified files. But it also lets you choose one or more paths instead. This adds significant complexity to `x fmt`. Explicit paths are specified via `WalkBuilder::add` rather than `OverrideBuilder::add`. The `ignore` library is not simple, and predicting the interactions between the two mechanisms is difficult. Here's a particularly interesting case. - You can request a path P that is excluded by the `ignore` list in the `rustfmt.toml`. E.g. `x fmt tests/ui/` or `x fmt tests/ui/bitwise.rs`. - `x fmt` will add P to the walker (via `WalkBuilder::add`), traverse it (paying no attention to the `ignore` list from the `rustfmt.toml` file, due to the different mechanism), and call `rustfmt` on every `.rs` file within it. - `rustfmt` will do nothing to those `.rs` files, because it *also* reads `rustfmt.toml` and sees that they match the `ignore` list! It took me *ages* to debug and understand this behaviour. Not good! `x fmt` even lets you name a path below the current directory. This was intended to let you do things like `x fmt std` that mirror things like `x test std`. This works by looking for `std` and finding `library/std`, and then formatting that. Unfortuantely, this motivating case now gives an error. When support was added in #107944, `library/std` was the only directory named `std`. Since then, `tests/ui/std` was added, and so `x fmt std` now gives an error. In general, explicit paths don't seem particularly useful. The only two cases `x fmt` really needs are: - format/check the files I have modified (99% of uses) - format/check all files (While respecting the `ignore` list in `rustfmt.toml`, of course.) So this commit moves to that model. `x fmt` will now give an error if given an explicit path. `x fmt` now also supports a `--all` option. (And running with `GITHUB_ACTIONS=true` also causes everything to be formatted/checked, as before.) Much simpler!
2024-04-22introduce `x vendor`onur-ozkan-1/+250
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-04-05Auto merge of #123317 - RalfJung:test-in-miri, r=m-ou-se,saethlin,onur-ozkanbors-1/+263
Support running library tests in Miri This adds a new bootstrap subcommand `./x.py miri` which can test libraries in Miri. This is in preparation for eventually doing that as part of bors CI, but this PR only adds the infrastructure, and doesn't enable it yet. `@rust-lang/bootstrap` should this be `x.py test --miri library/core` or `x.py miri library/core`? The flag has the advantage that we don't have to copy all the arguments from `Subcommand::Test`. It has the disadvantage that most test steps just ignore `--miri` and still run tests the regular way. For clippy you went the route of making it a separate subcommand. ~~I went with a flag now as that seemed easier, but I can change this.~~ I made it a new subcommand. Note however that the regular cargo invocation would be `cargo miri test ...`, so `x.py` is still going to be different in that the `test` is omitted. That said, we could also make it `./x.py miri-test` to make that difference smaller -- that's in fact more consistent with the internal name of the command when bootstrap invokes cargo. `@rust-lang/libs` ~~unfortunately this PR does some unholy things to the `lib.rs` files of our library crates.~~ `@m-ou-se` found a way that entirely avoids library-level hacks, except for some new small `lib.miri.rs` files that hopefully you will never have to touch. There's a new hack in cargo-miri but there it is in good company...
2024-04-03add 'x.py miri', and make it work for 'library/{core,alloc,std}'Ralf Jung-1/+263
2024-04-02x.py test: remove no-op --skip flagRalf Jung-8/+8
2024-01-11Auto merge of #119654 - onur-ozkan:bump-dependencies, r=clubby789bors-1/+5
bump bootstrap dependencies This PR removes hard-coded patch versions, updates bootstrap's dependency stack to recent versions (some of the versions were released 3-4 years ago), and removes a few dependencies from bootstrap. Removed dependencies: ![image](https://github.com/rust-lang/rust/assets/39852038/95e86325-aea0-4055-bee5-245c144f662e)
2024-01-11bless tidyonur-ozkan-1/+5
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2024-01-01pass allow-{dirty,staged} to clippyonur-ozkan-1/+7
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-12-11update auto completionsonur-ozkan-15/+60
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-12-09allow bypassing the build directory lockonur-ozkan-40/+85
As bootstrap locks its entire build directory, parallel bootstrapping for anything becomes impossible. This change enables developers to bypass the locking mechanism when it is unnecessary for their specific use case. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-22add bootstrap flag `--skip-stage0-validation`onur-ozkan-15/+60
This change introduces the --skip-stage0-validation flag, which permits the use of any desired version of the stage0 compiler without verifying its version. Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-15generate zsh autocompletion for xonur-ozkan-0/+751
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-15bump bootstrap:clap_complete to `4.4.3`onur-ozkan-50/+50
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2023-10-09Add `--enable-bolt-settings` bootstrap flagJakub Beránek-15/+45
2023-08-10Auto merge of #112482 - tgross35:ci-non-rust-linters, r=pietroalbinibors-1/+7
Add support for tidy linting via external tools for non-rust files This change adds the flag `--check-extras` to `tidy`. It accepts a comma separated list of any of the options: * py (test everything applicable for python files) * py:lint (lint python files using `ruff`) * py:fmt (check formatting for python files using `black`) * shell or shell:lint (lint shell files using `shellcheck`) Specific files to check can also be specified via positional args. Examples: * `./x test tidy --check-extras=shell,py` * `./x test tidy --check-extras=py:fmt -- src/bootstrap/bootstrap.py` * `./x test tidy --check-extras=shell -- src/ci/*.sh` * Python formatting can be applied with bless: `./x test tidy --ckeck-extras=py:fmt --bless` `ruff` and `black` need to be installed via pip; this tool manages these within a virtual environment at `build/venv`. `shellcheck` needs to be installed on the system already. --- This PR doesn't fix any of the errors that show up (I will likely go through those at some point) and it doesn't enforce anything new in CI. Relevant zulip discussion: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Other.20linters.20in.20CI
2023-08-06fix(bootstrap): rename exclude flag to skip 🐛Meysam Azad-15/+99
2023-08-02Add support for tidy linting via external tools for non-rust filesTrevor Gross-1/+7
This change adds the flag `--check-extras` to `tidy`. It accepts a comma separated list of any of the options: - py (test everything applicable for python files) - py:lint (lint python files using `ruff`) - py:fmt (check formatting for python files using `black`) - shell or shell:lint (lint shell files using `shellcheck`) Specific files to check can also be specified via positional args. Examples: - `./x test tidy --check-extras=shell,py` - `./x test tidy --check-extras=py:fmt -- src/bootstrap/bootstrap.py` - `./x test tidy --check-extras=shell -- src/ci/*.sh` - Python formatting can be applied with bless: `./x test tidy --ckeck-extras=py:fmt --bless` `ruff` and `black` need to be installed via pip; this tool manages these within a virtual environment at `build/venv`. `shellcheck` needs to be installed on the system already.
2023-07-31Remove BOLT from bootstrapJakub Beránek-90/+60
2023-07-30support `--stage` for `x clean`ozkanonur-9/+9
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-05-24Auto merge of #111566 - clubby789:bootstrap-override-config, r=ozkanonurbors-15/+105
Override config.toml options from command line https://rust-lang.zulipchat.com/#narrow/stream/326414-t-infra.2Fbootstrap/topic/Running.20tests.20on.20precompiled.20rustc/near/357763280 cc `@jyn514`
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 16:34:56 +0000