Skip to content

Clarify RFC merge instructions#1056

Open
carols10cents wants to merge 1 commit into
rust-lang:masterfrom
carols10cents:rfc-merge-procedure
Open

Clarify RFC merge instructions#1056
carols10cents wants to merge 1 commit into
rust-lang:masterfrom
carols10cents:rfc-merge-procedure

Conversation

@carols10cents
Copy link
Copy Markdown
Member

@carols10cents carols10cents commented May 27, 2026

What happened

I don't merge RFCs very often, so I went looking for instructions on how to merge them. I happened across this page and started following the instructions-- then found I don't actually have permission to push directly to rust-lang/rfcs master 😅

The instructions said "Open a PR" so I did, even though that felt strange rather than just pushing them to my RFC's PR, and then I was informed that what I did was indeed strange.

Fix

So I rearranged these instructions to first split based on permissions, then direct those without permissions to add to their existing PR rather than making a new one (assuming the person merging is the PR author, which I believe to be the usual case).

Rendered

If you can't push directly to the repo, the commits moving the RFC file
and adding links can be pushed to the RFC's branch and merged with the
RFC PR, not in a new PR.
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label May 27, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented May 27, 2026

r? @scottmcm

rustbot has assigned @scottmcm.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: lang
  • lang expanded to joshtriplett, nikomatsakis, scottmcm, tmandry, traviscross
  • Random selection from joshtriplett, nikomatsakis, scottmcm, tmandry, traviscross

### Step 2: Merge the RFC PR itself

In your local git checkout:
If you have permissions to push directly to rust-lang/rfcs, then in your local git checkout:
Copy link
Copy Markdown
Contributor

@ehuss ehuss May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everyone in the org has the same write permissions on rust-lang/rfcs. Can you say why it seemed like you didn't have the ability to push?

Generally there shouldn't ever be a need to open a new PR.

View changes since the review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants