-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Switch CI to new metadata collection #7298
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.
The deployment script has some special handling for tags and the beta deployment (if I understand it correctly). In #7279 we've discussed that a stable
branch should be added to support the View Code link works for all website paths. I believe that should be added to the deployment script as well.
The rest looks straight forward and should hopefully work. You mentioned that you've wanted to document the CI a bit better. Do you want to do that as part of this PR or after everything works?
Thank you for taking over the CI work :)
Another question that I had recently that is slightly related: The Clippy CI currently starts on every push even in forks or it at least does for me xFrednet/rust-clippy/actions. Is that intended behavior? I'm fine with it eating up my CI time, but other users might not be in favor of it.
Quite the opposite. The
Thanks for reminding / forcing me to do this. I want to do this separately. In this PR I only want the really necessary things, so if something goes wrong, we can just revert one commit and everything is fine again.
Yes, this only applies for the |
Yes, that's what I meant.
Sure, makes sense. I remember reading the documentation one or two times before my first contribution to not ask any stupid questions. And it stayed in my focus since then to help other newcomers as well 🙃
Okay, thanks for confirming 👍 |
97d1f7f
to
76a06e5
Compare
This deploy workflow run won't actually work. For that I have to reopen this PR from a branch directly in this repo. |
@xFrednet I think I addressed everything we discussed in your previous review. Before I push it to a branch in this repo for testing, can you take another look, if you still notice things that might need another 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.
The rest looks ready for a test IMO 👍
Is it intended, that the CI is red in this PR?
I guess you mean "red"? Or do you mean that it is run? In the first case not intended, but expected, in the second, yes. |
Yes 😅 Everything should be covered in that case :) |
76a06e5
to
77187c9
Compare
77187c9
to
6390275
Compare
Alright, I tested everything in #7401. So we should be ready for the move, after I squashed the commits. I won't get to do this this weekend, but plan to do it next Saturday 2021-07-03 |
Awesome!!! I'll review this PR again and also look at the test. Next weekend also works for me, I'll rebase #7279 and create a new PR (shortly before the switch) to update the documentation to use hashtags instead of bold text. Is there anything else you need help with? 🙃 |
Nope, I think I'm good 👍 |
6390275
to
5d412c0
Compare
This isn't the case anymore, since I decided to break the stable deploy for one cycle and do it by hand instead. |
This updates all the deploy scripts and the deploy workflow. The deploy workflow now runs the metadata collector to collect the lint documentation. It also changes the files that are checked out in the deploy workflow from master and adds an explanation why we have to do this.
5d412c0
to
fe25282
Compare
@bors r=xFrednet,flip1995 rollup |
📌 Commit fe25282 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. |
…ednet,flip1995 Switch CI to new metadata collection r? `@xFrednet` Things we have to keep in mind: - This removes the template files and the scripts used for deployment from the checkout. This was added in rust-lang#5517. I don't think we ever needed those there. Not sure though. - ~~As a result, we can't remove the python scripts yet. We have to wait until this hits a stable Clippy release.~~ I'll just break the next stable deploy and do it by hand once. - This should be merged together with rust-lang#7279. Me and `@xFrednet` will coordinate the switch - ...? I still have to try out some things: - [x] Is it worth caching? Yes - [x] ~~Is it worth to do a release build?~~ Nope - [x] Does it actually work? With a few changes, yes - [ ] ...? changelog: Clippy now uses a lint to generate its documentation 🎉
@bors r=xFrednet,flip1995 rollup |
📌 Commit c951a3c 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
r? @xFrednet
Things we have to keep in mind:
As a result, we can't remove the python scripts yet. We have to wait until this hits a stable Clippy release.I'll just break the next stable deploy and do it by hand once.I still have to try out some things:
Is it worth to do a release build?Nopechangelog: Clippy now uses a lint to generate its documentation 🎉