rustc-dev-guide: Rfcbot Labels and Helpful Links

[rfcbot] uses its own labels for tracking the process of coordinating asynchronous decisions, such as approving or rejecting a change. This is used for [RFCs], issues, and pull requests. | Labels | Color | Description | |--------|-------|-------------| | [proposed-final-comment-period] |   Gray | Currently awaiting signoff of all team members in order to enter the final comment period. | | [disposition-merge] |   Green | Indicates the intent is to merge the change. | | [disposition-close] |   Red | Indicates the intent is to not accept the change and close it. | | [disposition-postpone] |   Gray | Indicates the intent is to not accept the change at this time and postpone it to a later date. | | [final-comment-period] |   Blue | Currently soliciting final comments before merging or closing. | | [finished-final-comment-period] |   Light Yellow | The final comment period has concluded, and the issue will be merged or closed. | | [postponed] |   Yellow | The issue has been postponed. | | [closed] |   Red | The issue has been rejected. | | [to-announce] |   Gray | Issues that have finished their final-comment-period and should be publicly announced. Note: the rust-lang/rust repository uses this label differently, to announce issues at the triage meetings. | [disposition-merge]: https://github.com/rust-lang/rust/labels/disposition-merge [disposition-close]: https://github.com/rust-lang/rust/labels/disposition-close [disposition-postpone]: https://github.com/rust-lang/rust/labels/disposition-postpone [proposed-final-comment-period]: https://github.com/rust-lang/rust/labels/proposed-final-comment-period [final-comment-period]: https://github.com/rust-lang/rust/labels/final-comment-period [finished-final-comment-period]: https://github.com/rust-lang/rust/labels/finished-final-comment-period [postponed]: https://github.com/rust-lang/rfcs/labels/postponed [closed]: https://github.com/rust-lang/rfcs/labels/closed [to-announce]: https://github.com/rust-lang/rfcs/labels/to-announce [rfcbot]: https://github.com/anp/rfcbot-rs/ [RFCs]: https://github.com/rust-lang/rfcs ## Helpful links and information This section has moved to the ["About this guide"] chapter. ["About this guide"]: about-this-guide.md#other-places-to-find-information [search existing issues]: https://github.com/rust-lang/rust/issues?q=is%3Aissue [Breaking Changes]: bug-fix-procedure.md [triagebot.toml config file]: https://github.com/rust-lang/rust/blob/HEAD/triagebot.toml [rust-lang teams database]: https://github.com/rust-lang/team/tree/HEAD/teams [compiler test suite]: tests/intro.md [merge queue]: https://bors.rust-lang.org/queue/rust [git hooks]: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks [A-docs label]: https://github.com/rust-lang/rust/issues?q=is%3Aopen%20is%3Aissue%20label%3AA-docs [RFC 1574]: https://github.com/rust-lang/rfcs/blob/master/text/1574-more-api-documentation-conventions.md#appendix-a-full-conventions-text [rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/ [rdgrepo]: https://github.com/rust-lang/rustc-dev-guide

This section explains the different labels used by Rfcbot for tracking asynchronous decisions on RFCs, issues, and pull requests, including labels such as `final-comment-period`, `finished-final-comment-period`, `postponed`, `closed`, and `to-announce`. It also provides a list of helpful links and information, now moved to the "About this guide" chapter, including links to search existing issues, breaking changes procedure, triagebot configuration, rust-lang teams database, and more.