Skip to content

Explain where rdg changes should be submitted #909

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 28, 2025
Merged

Explain where rdg changes should be submitted #909

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/wg-rustc-dev-guide/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,16 @@ A good rule of thumb for whether you should feel comfortable merging your own ru
you would feel comfortable approving an involved PR touching the relevant area of the compiler. See the
compiler [review policy](../compiler/reviews.md).

## Where to contribute `rustc-dev-guide` changes

If your change **only involves the documentation content of rustc-dev-guide** and **does not accompany `rust-lang/rust` code changes**,
please submit your changes and PRs directly to the [rust-lang/rustc-dev-guide](https://github.com/rust-lang/rustc-dev-guide) repository.

There are some benifits following this rule:
- Changes to `rustc-dev-guide` repo can be immediately reflected in [the live rustc-dev-guide](https://rustc-dev-guide.rust-lang.org/).
- Changes to `rustc-dev-guide` repo do not need to go through bors CI in `rust-lang/rust`.
- Less burden on bors queue in `rust-lang/rust`.

## Subtree Syncs

The dev guide is a [josh](https://josh-project.github.io/josh/intro.html) subtree of the main rust-lang/rust
Expand Down