The RFC production Center is modernizing their tools infrastructure and will be using GitHub for version control in 2026 (please see the RPC GitHub roadmap for details). However, before the full solution is rolled out, the RPC intends to offer AUTH48 GitHub repos on a limited basis as a transitional step so we can support those authors that want to use GitHub for AUTH48 sooner. This process will be offered to authors whose documents are entering the RFC Editor Queue starting 1 November 2025.

The goal is to further support the authoring community and facilitate author reviews using tools they are familiar with.

To start, the RPC will accept at least 5 GitHub AUTH48 requests per month. The RPC will ask authors if they want to participate when their document enters the queue. If so, then RPC will do the following when the document enters AUTH48:

• Create a GitHub repository in the rfc-editor organization
• Add the approved source file to the repo
• Add questions regarding the document in the issue tracker
• Create a pull request (PR) containing all RPC proposed edits

Note that authors can choose to participate in this pilot program and also the kramdown-rfc pilot program.

Authors will provide feedback on the RFC-to-be using GitHub's review and issue-tracking tools. Once the authors approve changes, the PR will be merged. If the document source is kramdown-rfc, there will be an additional step of approving the RFCXML and output formats.

We expect to pilot this process while our version control solution is being developed. We thank you in advance for your patience while we work through the process kinks.

For more information about RPC projects, please see:

• RPC Roadmap
• RPC Community Calls