diff options
| author | bors <bors@rust-lang.org> | 2023-11-23 09:04:46 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-23 09:04:46 +0000 |
| commit | 30c743f8a04d2ad35885eefaa8d29b19a0e3d013 (patch) | |
| tree | 978cf498f75cf4f0309ccc0ebdf1f5328ce71cd2 /compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp | |
| parent | c24784ed812cd4956855c2b5eb4059cf638cea9e (diff) | |
| parent | c18e6abdca0022acc022b65fa5d239d800728693 (diff) | |
| download | rust-30c743f8a04d2ad35885eefaa8d29b19a0e3d013.tar.gz rust-30c743f8a04d2ad35885eefaa8d29b19a0e3d013.zip | |
Auto merge of #11857 - matthri:add-collect-metadata-note, r=flip1995
Add documentation update hint using `cargo collect-metadata` This adds a little reminder to update the documentation in the book using `cargo collect-metadata` after changing the lint configuration since this can easily be missed (been there done that 🙈). > Yeah a note would be good, would be good for us to see if we can make it automatic also _Originally posted by `@Alexendoo` in https://github.com/rust-lang/rust-clippy/issues/11757#issuecomment-1823474156_ Regarding the automation Im not sure whats the best option here. I thought about a kind of a "semi-automated" way, e.g. a `cargo dev` command which runs the "is the documentation updated" check (and maybe other useful checks) locally and reminds the user of updating the documentation so this gets caught before pushing. changelog: none
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp')
0 files changed, 0 insertions, 0 deletions