-
Notifications
You must be signed in to change notification settings - Fork 914
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
Stabilize ignore config option #4139
Conversation
@@ -1063,7 +1063,7 @@ The pattern format is the same as [.gitignore](https://git-scm.com/docs/gitignor | |||
|
|||
- **Default value**: format every file | |||
- **Possible values**: See an example below | |||
- **Stable**: No (tracking issue: [#3395](https://github.com/rust-lang/rustfmt/issues/3395)) | |||
- **Stable**: Yes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I will fix that first. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI failures are spurious, presumably related to the current GH status issues error: failed to get `ansi_term` as a dependency of package `rustfmt-bin v2.0.0-rc.1 (/Users/travis/build/rust-lang/rustfmt/rustfmt-core/rustfmt-bin)`
Caused by:
failed to load source for dependency `ansi_term`
Caused by:
Unable to update registry `https://github.com/rust-lang/crates.io-index`
Caused by:
failed to fetch `https://github.com/rust-lang/crates.io-index`
|
Should this work by now?
|
Can confirm the same error with a slightly older version, too.
|
Same here:
|
Was this commit excised from master after commit? I cannot find it in the master branch history, or in the contents of the files this PR was supposed to change. |
I have the same issue in august releases |
Issue persisted in:
|
All - your definitive source of truth around which rustfmt configuration options are available, as well as which are stable/unstable, in the version of rustfmt you are using is the configuration website: https://rust-lang.github.io/rustfmt/?version=v1.4.38&search=#ignore Changes made to source control are not reflective of any and all released versions of software, especially in multibranch repositories, and the This change was originally made against an exploratory 2.0 version of rustfmt along with a multitude of other breaking changes. That 2.0 version of rustfmt is unlikely to happen (at least any time soon), and as such that version is no longer being tracked on the default/master branch of this repository which is why the commits from this, and other 2.0-bound PRs do not exist on the current master branch, refs #4801. It also means that there are merged PRs and associated closed issues which haven't actually made their way into a release line. There's a large number of such changes that were made for that potential 2.0 release which we have to revisit individually, including this one, and I'd ask that folks refrain from continuing to post the "me too" types of comments; it's known, and the issues are being tracked. In the interim, I would again encourage always referencing the config site and check the actual release notes for details on what's indeed been released. |
This remains broken in 2024.
|
@rdaum please see #3243 (comment) |
Close #3243.