-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Redirect nightly doc to doc.rust-lang.org/nightly/nightly-rustc/cargo
#11555
Comments
cc @epage, as you participated in the PR building API doc. I personally favor keeping only https://doc.rust-lang.org/nightly/nightly-rustc/cargo though is fine with having both. |
I'm fine with that. I assume the main side effect is it isn't updated until rust-lang/rust updates their copy of cargo? |
Yep. That's the main one. I cannot think of others at this moment though. |
Hi, |
Thank you for asking! The words might be a bit too strong but the team does have a limited capacity for both design and code review. The idea here is to encourage people to start a discussion from an issue before submitting a pull request. In general, with
E-easy
If you are willing to help a certain issue, you could optionally post a comment |
Great, thank you! |
@rustbot claim |
I'm not quite sure which |
Oops that's my fault. And yes, you're totally correct! I believe that should work. |
Fix for #11555 Fix for #11555. I more or less blindly followed the instructions given by `@weihanglo` in the description of the issue: 1. I replaced every link from `doc.crates.io/contrib/apidoc/cargo` with `doc.rust-lang.org/nightly/nightly-rustc/cargo` 2. Added redirection rule to `src/doc/contrib/book.toml` that should redirect the `/apidoc/cargo/` endpoint to `https://doc.rust-lang.org/nightly/nightly-rustc/cargo` 3. Reverted the changes made to the CI workflow in ba3d2e9 and 1c82d9c (building the api docs as part of the contribution guide)
8 commits in d992ab4e9034930e7809749f04077045af8f4d79..1cd6d3803dfb0b342272862a8590f5dfc9f72573 2023-01-10 14:36:41 +0100 to 2023-01-12 18:40:36 +0000 - Fix for rust-lang/cargo#11555 (rust-lang/cargo#11568) - chore: Fix typos (rust-lang/cargo#11561) - fix(docs): fix typo learm => learn in cargo tree docs (rust-lang/cargo#11560) - Add fix for CVE-2022-46176 (rust-lang/cargo#11556) - Fix panic on target dependency errors. (rust-lang/cargo#11541) - Fix some doc links (rust-lang/cargo#11538) - Cargo by default saves credentials to `.cargo/credentials.toml` (rust-lang/cargo#11533) - Fix a typo in the registries documentation. (rust-lang/cargo#11535)
Update cargo 8 commits in d992ab4e9034930e7809749f04077045af8f4d79..1cd6d3803dfb0b342272862a8590f5dfc9f72573 2023-01-10 14:36:41 +0100 to 2023-01-12 18:40:36 +0000 - Fix for rust-lang/cargo#11555 (rust-lang/cargo#11568) - chore: Fix typos (rust-lang/cargo#11561) - fix(docs): fix typo learm => learn in cargo tree docs (rust-lang/cargo#11560) - Add fix for CVE-2022-46176 (rust-lang/cargo#11556) - Fix panic on target dependency errors. (rust-lang/cargo#11541) - Fix some doc links (rust-lang/cargo#11538) - Cargo by default saves credentials to `.cargo/credentials.toml` (rust-lang/cargo#11533) - Fix a typo in the registries documentation. (rust-lang/cargo#11535)
Problem
After rust-lang/rust#105036, docs of Cargo and its companion crates are live now at https://doc.rust-lang.org/nightly/nightly-rustc.
I wonder whether https://doc.crates.io/contrib/apidoc/cargo should be redirected to that "canonical" URL. It might be more discoverable as all rustc internal docs are already there, whereas the doc will only get updated when cargo gets synced into
rust-lang/rust
repo, which happens only once or twice a week.Proposed Solution
Follow the steps:
doc.crates.io/contrib/apidoc/cargo
withdoc.rust-lang.org/nightly/nightly-rustc/cargo
in this repo.book.toml
from/apidoc/cargo
tohttps://doc.rust-lang.org/nightly/nightly-rustc/cargo
.Notes
No response
The text was updated successfully, but these errors were encountered: