-
Notifications
You must be signed in to change notification settings - Fork 302
Add blog post about recent Clippy team changes #999
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
Conversation
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.
r? @rylev
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.
Looks great! We might have another post in the docket for today (though on the main blog and not the inside-rust blog). We may want to hold off until 04-July to post. In the meantime, there's a few nits to sort through.
This comment was marked as resolved.
This comment was marked as resolved.
Just noticed that this is PR #999. Sooo close 🥲 |
ping @rylev. When would you suggest to release this post? I'll adapt the date of the post accordingly. |
@flip1995 sorry for the delay - I was on holiday last week. Does tomorrow (2022-07-12) work? |
9794c64
to
f5b744d
Compare
Works for me. I squashed+rebased the post and updated the date to tomorrow 👍 |
f5b744d
to
8864664
Compare
ping @rylev bumped the date to today. Yesterday this would've interfered with the core team update. I would like to get this merged rather sooner than later now. |
@flip1995 it has been merged! Thanks for your patience! |
We changed the Clippy team quite a bit recently with 3 new team additions. We want to get this a little bit more visibility and decided to write up a blog post, like other teams do.
cc @rust-lang/clippy