acoustic-carpenter-78188
04/28/2026, 6:25 PMmain for Flyte 2 and master for Flyte 1). Triagers currently have to manually label PRs to distinguish which line they target, which is easy to miss.
What changes were proposed in this pull request?
Adds an actions/labeler@v5 workflow that automatically labels PRs based on their base branch:
• PRs targeting main get the flyte2 label
• PRs targeting master get the flyte label
Files added:
• .github/labeler.yml — labeler configuration using base-branch regex matching
• .github/workflows/labeler.yml — workflow triggered on PR open/reopen/sync, with pull-requests: write permission
sync-labels: false so the action only adds labels and never removes user-applied ones.
How was this patch tested?
Workflow will run on this PR itself — expect the flyte2 label to be applied automatically once merged, since this PR targets main.
Note: the flyte and flyte2 labels need to exist in the repo's label set for the action to apply them.
Check all the applicable boxes
• All commits are signed-off.
flyteorg/flyteacoustic-carpenter-78188
04/28/2026, 6:32 PMacoustic-carpenter-78188
04/28/2026, 6:32 PMacoustic-carpenter-78188
04/29/2026, 12:54 AM