This repository was archived by the owner on Nov 19, 2025. It is now read-only.

Description
Area
No response
Problem
Creating an RFC involves several tasks unrelated to drafting it, but should still get done. This includes filling out the fields at the top of the RFC, assigning a file name, and collecting useful things in the PR message. This might lead to mistakes, and is just plain not fun to do. This is also largely the case with merging RFCs.
Suggested solution
This could be handled by a GitHub Actions-based bot, that triggers whenever a pull request with the RFC tag is created. A pull request template could be created to still allow the author to include additional information.
This bot would basically handle all the manual tasks outside of writing the actual RFC and giving feedback.
Alternatives
We could just not do this, and that's perfectly fine if we have few actual RFCs to manage.
Additional information
This was largely just an idea I had and wanted to write down, that may or may not turn out useful. It's very low priority. I might add more details later on.
Checks