-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Update lint documentation to use markdown headlines #7420
Update lint documentation to use markdown headlines #7420
Conversation
r? @flip1995 seems like |
Yeah, it seems GitHub recently has problems with webhooks, so the bots are a bit flaky. As you may have noticed: I didn't get to the move this weekend and try to fit it in during this week. |
☔ The latest upstream changes (presumably #7462) made this pull request unmergeable. Please resolve the merge conflicts. |
I'm actually surprised it took this long xD. I'll update the PR in the next couple of days (hopefully tomorrow) |
3a25292
to
2d26817
Compare
self_named_constructor lint was added |
Thank you for the ping! I'll update this PR tomorrow 🙃 |
2d26817
to
bb9cdea
Compare
☔ The latest upstream changes (presumably #7482) made this pull request unmergeable. Please resolve the merge conflicts. |
bb9cdea
to
5eeff3c
Compare
☔ The latest upstream changes (presumably #7488) made this pull request unmergeable. Please resolve the merge conflicts. |
5eeff3c
to
ffa8de9
Compare
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.
LGTM overall. This messes up the formatting of the in-code documentation a bit (line length of the first doc line) but we weren't consistent in that regard anyway. Also it won't have any influence on the website.
I'll merge this after the move.
@@ -11,6 +11,7 @@ because that's clearly a non-descriptive name. | |||
- [Setup](#setup) | |||
- [Getting Started](#getting-started) | |||
- [Testing](#testing) | |||
- [Cargo lints](#cargo-lints) |
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.
Ninja fix 😄
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.
xD even for me. A IDE plugin did that and I only noticed it when I reviewed the changes on GitHub xD
I would also suggest merging this last, another idea I had was to crate a rollup PR that combines all metadata related PRs 🤔 You'll find a good solution, I have faith in you 🙃
@bors r+ rollup |
📌 Commit 906464e has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000. This pull request will be tested once the tree is reopened. |
…ion, r=flip1995 Update lint documentation to use markdown headlines This PR updates all lint documentation to use markdown headlines. It additionally removed the *Known problems* section for lints without any problems. I've double-checked all automatic replacements, but a second pair of eyes is definitely appreciated! I wasn't sure when you wanted to switch to the new metadata collection tomorrow, I therefore prepared this PR today. And that's it this is a standalone PR to keep the other related PRs reviewable. changelog: none r? `@flip1995` cc: rust-lang#7172 Note: This should be merged with the other metadata collection related PRs.
906464e
to
9bc5803
Compare
@bors r+ rollup |
📌 Commit 9bc5803 has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000. This pull request will be tested once the tree is reopened. |
Updated changelog for 1.55 This has again been a bit of work, but I'm happy to notice that my English is still improving, and I'm getting faster at these things. That's a very nice side effect of contributing and getting feedback on reviews 😊 Moving on, there were a few things that I was unsure about: * The PR rust-lang/rust#86717 changes an old entry in the change log, is this worth mentioning? I've left it out for now. * The stabilization of `cargo clippy --fix` is quite awesome and important IMO. It sadly gets a bit lost in the *Other* entry, as it's the last one. Do we maybe want to move it somewhere else or change the headline order for this release? * I've listed the introduction of the new `suspicious` group under the *Moves and Deprecations* section. Is this alright, or should it be moved to the *Other* section as well? * Last but definitely not least, some fun! I've used the 🎉 emoji in the `cargo clippy --fix` entry, is this okay? Sorry for the bombardment of questions xD --- The PR already includes the entries for the new metadata collection and website updates. These are not merged yet, but should probably be to make this correct. This might also require the commit hashes to be updated (Not sure on this, though). It would actually be super fitting to get this into this release as we also stabilize `--fix`. TODOs: * [x] Merge metadata collection PRs: 1. #7279 2. #7298 3. #7420 (Hope to not get any merge conflicts) --- [Rendered 📰](https://github.com/xFrednet/rust-clippy/blob/changelog-1-55/CHANGELOG.md) r? `@flip1995` changelog: none
This PR updates all lint documentation to use markdown headlines. It additionally removed the Known problems section for lints without any problems. I've double-checked all automatic replacements, but a second pair of eyes is definitely appreciated!
I wasn't sure when you wanted to switch to the new metadata collection tomorrow, I therefore prepared this PR today. And that's it this is a standalone PR to keep the other related PRs reviewable.
changelog: none
r? @flip1995
cc: #7172
Note: This should be merged with the other metadata collection related PRs.