Skip to content

Commit ef30fc7

Browse files
docs(ci): mark the legacy backport label arms as transitional
The dual acceptance exists so the rename can land in any order relative to disabling dosubot's PR labelling, not because two spellings are wanted long term. Naming the deletion sites keeps that from becoming permanent by default. Assisted-By: Claude <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent ab0917b commit ef30fc7

1 file changed

Lines changed: 7 additions & 4 deletions

File tree

‎.github/workflows/backport.yaml‎

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -144,10 +144,13 @@ jobs:
144144
script: |
145145
const pr = context.payload.pull_request;
146146
const labels = pr.labels.map(l => l.name);
147-
// Both spellings are accepted on purpose. The namespaced names are
148-
// the convention this repo declares, but the org-level dosubot still
149-
// applies the legacy ones and it is the dominant applier on real
150-
// backports, so dropping them would silently stop the bot for those.
147+
// TRANSITIONAL: both spellings are accepted so the rename can land
148+
// in any order relative to the org-level dosubot, which still
149+
// applies the legacy names and is today the dominant applier on
150+
// real backports. Once dosubot's PR labelling is switched off and
151+
// the in-repo labeler is the only applier, the legacy arms here,
152+
// in the `if:` gate above and in the concurrency group can all be
153+
// deleted in one pass.
151154
const isBackport = labels.includes('kind/backport') || labels.includes('backport');
152155
const isBackportPrevious = labels.includes('kind/backport-previous') || labels.includes('backport-previous');
153156

0 commit comments

Comments
 (0)