Skip to content

Add dev-tools peer groups to rfcbot #153

Closed
@QuietMisdreavus

Description

@QuietMisdreavus

internals.rust-lang.org announcement post (alongside the infra and cargo teams)

It looks like the core dev-tools team has been added, but for RFCs that primarily concern a specific tool, like RFC 1946 for Rustdoc, it may be necessary to add the peers for that tool to the FCP checklist. The individual peer groups are listed in the announcement post linked above. According to @aturon and @nrc, the plan is to have separate tags for each tool, like T-dev-tools-rustdoc on the aforementioned RFC, and to tag both T-dev-tools and T-dev-tools-foo (for some tool "foo") to pull in the core dev-tools team and the peers for that specific tool.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions