Skip to content

Explain where rdg changes should be submitted #2481

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

Merged
merged 1 commit into from
Jun 28, 2025

Conversation

xizheyin
Copy link
Contributor

r? rustc-dev-guide

@rustbot rustbot added the S-waiting-on-review Status: this PR is waiting for a reviewer to verify its content label Jun 26, 2025
@xizheyin xizheyin force-pushed the submit-in-rdg-or-r branch 2 times, most recently from 8feea7b to 4ef58f2 Compare June 26, 2025 15:03
@BoxyUwU
Copy link
Member

BoxyUwU commented Jun 26, 2025

I would prefer the docs to live in rust-forge and then just be linked from the dev guide as it's likely we'll want to link to them from the bot message in rust-lang/rust 🤔

@jieyouxu
Copy link
Member

Yeah, I think that might be more... logistically sound? Cuz this is like public-contributing-facing docs mostly, right?

@BoxyUwU
Copy link
Member

BoxyUwU commented Jun 26, 2025

Yeah it feels like dev-guide wg policy to me, and I think typically we prefer to put that in rustforge instead of in our README or a CONTRIBUTING or wherever

@jieyouxu
Copy link
Member

@xizheyin could you change this PR instead to back link to the Forge docs? Thanks

@xizheyin xizheyin force-pushed the submit-in-rdg-or-r branch from 4ef58f2 to 3407b01 Compare June 28, 2025 07:38
@xizheyin
Copy link
Contributor Author

Ok, it's done

@tshepang tshepang merged commit b47ab90 into rust-lang:master Jun 28, 2025
1 check passed
@xizheyin xizheyin deleted the submit-in-rdg-or-r branch June 28, 2025 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: this PR is waiting for a reviewer to verify its content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants