Skip to content
Coordinates asynchronous decision making on Rust repositories. Status of tracked issues and PRs can be viewed at
Rust TSQL HTML Shell
Branch: master
Clone or download
lzutao and Centril Rustup (#277)
* build: Update rust-toolchain

* build: Update deps to compatible version

chrono          0.4.6    0.4.7
reqwest         0.9.15   0.9.18
rocket          0.4.0    0.4.1
rocket_contrib  0.4.0    0.4.1
serde           1.0.90   1.0.93
serde_derive    1.0.90   1.0.93

* build: Update dotenv to 0.14.1

* build: Update env_logger and log

env_logger  0.4.3    ---     0.6.1   Normal  ---
log         0.3.9    ---     0.4.6   Normal  ---

* build: Update urlencoded to 0.6.0

* build: Update lock file

    Removing conduit-mime-types v0.7.3
    Removing error v0.1.9
    Updating futures v0.1.27 -> v0.1.28
    Updating iron v0.5.1 -> v0.6.0
    Removing lazy_static v0.2.11
      Adding mime_guess v1.8.7
Latest commit 0041dfa Jun 26, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
migrations [Needs review] Feature: @rfcbot poll [teams] (#219) Aug 16, 2018
src Rustup (#277) Jun 26, 2019
.gitignore .gitignore: add rls/ May 15, 2018
.travis.yml Transfer to 2018 edition (#273) Apr 26, 2019 Accept multiple @rfcbot invocations per comment (#211) May 31, 2018
Cargo.toml Rustup (#277) Jun 26, 2019
LICENSE-APACHE Initial commit with errata and environment variable configuration. Apr 13, 2016
LICENSE-MIT Initial commit with errata and environment variable configuration. Apr 13, 2016
Procfile put prod env back Jan 5, 2018
rfcbot.toml Integrate with the team repo (#267) Mar 31, 2019
rustfmt.toml Run cargo fmt on whole project (#272) Apr 25, 2019 Test coverage for teams.toml. (#203) May 7, 2018


rfcbot manages asynchronous decision making on Rust issues and PRs. Status of Final Comment Periods can be viewed on the relevant dashboard page.

It listens for commands on all repositories owned by the rust-lang, rust-lang-nursery, and rust-lang-deprecated organizations.

While its intended usage is for RFCs, you can use its tracking on any issue or pull request which needs an async review/decision cycle.


rfcbot accepts commands in GitHub comments. All commands take the form:


The bot expects one command per comment, and the command must start on its own line, but otherwise the bot doesn't care if there's other text in the comment. This is valid:

@rfcbot fcp merge

But this is not:

TEXT @rfcbot fcp merge

Only the first of these commands will be registered:

@rfcbot concern FOO
@rfcbot concern BAR

Examples are in each section.

Command grammar

rfcbot accepts roughly the following grammar:

merge ::= "merge" | "merged" | "merging" | "merges" ;
close ::= "close" | "closed" | "closing" | "closes" ;
postpone ::= "postpone" | "postponed" | "postponing" | "postpones" ;
cancel ::= "cancel | "canceled" | "canceling" | "cancels" ;
review ::= "reviewed" | "review" | "reviewing" | "reviews" ;
concern ::= "concern" | "concerned" | "concerning" | "concerns" ;
resolve ::= "resolve" | "resolved" | "resolving" | "resolves" ;
poll ::= "ask" | "asked" | "asking" | "asks" |
         "poll" | "polled" | "polling" | "polls" |
         "query" | "queried" | "querying" | "queries" |
         "inquire" | "inquired" | "inquiring" | "inquires" |
         "quiz" | "quizzed" | "quizzing" | "quizzes" |
         "survey" | "surveyed" | "surveying" | "surveys" ;

team_label ::= "T-lang" | .. ;
team_label_simple ::= "lang" | .. ;
team_ping ::= "@"? "rust-lang/lang" | ..;
team_target ::= team_label | team_label_simple | team_ping ;

line_remainder ::= .+$ ;
ws_separated ::= ... ;

subcommand ::= merge | close | postpone | cancel | review
             | concern line_remainder
             | resolve line_remainder
             | poll [team_target]* line_remainder

invocation ::= "fcp" subcommand
             | "pr" subcommand
             | "f?" ws_separated
             | subcommand

grammar ::= "@rfcbot" ":"? invocation ;

Multiple occurrences of grammar are allowed in each comment you make on GitHub. This means that the following is OK:

@rfcbot merge

Some stuff you want to say...

@rfcbot concern foobar

Explain the concern...

Final Comment Period

Before proposing a final comment period on an issue/PR/RFC, please double check to make sure that the correct team label(s) has been applied to the issue. As of 9/17/16, rfcbot recognizes these labels:

  • Core: T-core
  • Language: T-lang
  • Libraries: T-libs
  • Compiler: T-compiler
  • Tools: T-tools
  • Documentation: T-doc

Proposing FCP

To propose an FCP, use @rfcbot fcp DISPOSITION where disposition is one of [merge|close|postpone]. You can also use @rfcbot pr DISPOSITION, which will be used in the future to improve the quality of status comments from the bot.

If the proposer is on one of the tagged subteams, rfcbot will create a tracking comment with a checklist of review requests. Once all review requests have been satisfied and any concerns have been resolved, it will post a comment to that effect. One week after the "FCP start" comment, it will post another follow-up comment saying that one week has passed.

rfcbot will only request reviews from members of the tagged team(s), and as of right now only supports reviews from teams that are tagged at the time an FCP is proposed.

Cancelling FCP

To cancel an FCP proposal after it's started, use @rfcbot fcp cancel. This will delete all records of the FCP, including any concerns raised (although their comments will remain).


To indicate that you've reviewed the FCP proposal, either check the box next to your name on the tracking comment, or use the command @rfcbot reviewed.


To register blocking concerns on the FCP proposal, use @rfcbot concern NAME_OF_CONCERN. The bot will parse up until the first newline after the command for the concern's name, and add it to the list of concerns in the tracking comment.

To indicate that your concern has been resolved, use @rfcbot resolved NAME_OF_CONCERN. Note that as of this writing, only the original author can mark their concern as resolved.

Note that only one concern per comment is allowed.

Feedback Requests

To request feedback from a user not on the tagged team(s), use @rfcbot f? @username. This will create an entry in the database which will be marked as resolved once that user has commented on the issue/PR. Note that these feedback requests will not block start/end of an FCP. If you need to block FCP on that user's feedback, you may want to create a new concern that you can resolve.

In a future update, the UI for the dashboard will be updated to display these feedback requests, but they don't show up anywhere right now.

Contributing, Code of Conduct, License

Please see

You can’t perform that action at this time.