Skip to content

[DO NOT MERGE] Permit bare fcp merge if there's only a single T-* team label#345

Draft
jieyouxu wants to merge 2 commits intorust-lang:masterfrom
jieyouxu:merge-no-explicit-teams
Draft

[DO NOT MERGE] Permit bare fcp merge if there's only a single T-* team label#345
jieyouxu wants to merge 2 commits intorust-lang:masterfrom
jieyouxu:merge-no-explicit-teams

Conversation

@jieyouxu
Copy link
Copy Markdown
Member

@jieyouxu jieyouxu commented Jan 2, 2026

Caution

The design of this needs some more discussion (thread: #t-infra > rfcbot down? @ 💬), should not be merged before that. Two things:

  1. Provided team `` is invalid #343 is because we try to split(",") even on empty team list, which still correspond to 1 iteration of the empty string as-is. That empty string then obviously isn't a valid team, so we produce an comment complaining that "``" is not a valid team. This feels unintentional and more of a bug.
  2. Explicit/implicit teams inconsistent between FCP dispositions #344 is the more over-arching UX inconsistency, because we currently only require "disambigutating explicit team list" for FCP merge when there's multiple team labels present, but not for other FCP dispositions {close,postpone}.

... with no explicit team list. Previously, when no explicit team list
is specified, we unconditionally rejected bare `fcp merge`
syntactically. The error message in the posted comment said

> Provided team `` is invalid

which doesn't help the FCP proposer figure out what's wrong.

This test currently fails.
Defer the "no explicit team list" check until the github nag check for
multiple team labels mandating team list specification. Previously, we
would reject bare `@rfcbot fcp merge` _syntactically_ based on absence
of explicit team list unconditionally.

Now, the behavior is that:

- In situation where there is exactly 1 `T-*` team label, `@rfcbot fcp
  merge` is permitted as a convenience fast-path, since this is
  unambiguous (for the most part).
- When there are more than 1 `T-*` team labels, `@rfcbot fcp merge` is
  rejected, since it's usually not clear if _all_ the teams
  corresponding to the `T-*` labels should be involved in the FCP, or
  only a single team, or only a subset of teams.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant