Add filtering options to auto-triage command#63300
Conversation
Add several new filtering criteria organized into logical groups: Filter options: - --label: now supports wildcards (e.g. 'area:*', 'provider:amazon*') - --exclude-label: exclude PRs by label, supports wildcards - --created-after/--created-before: date range for PR creation - --updated-after/--updated-before: date range for last update - --include-collaborators: include collaborator PRs (normally skipped) - --pending-approval-only: only show PRs needing workflow approval - --checks-state: filter by CI status (failure/success/pending/any) - --min-commits-behind: filter by staleness Exact labels and date ranges are pushed to GitHub search for efficiency. Wildcard labels are matched client-side with fnmatch after fetching. Option groups in pr_commands_config.py reorganized into: Target selection, Filter options, Pagination and sorting, Assessment options, Action options. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jscheffl
left a comment
There was a problem hiding this comment.
Starting to get owverwhelmed with options now :-D Do I need a LLM to start using all the options? :-D
Our new AgenticOperator 😄 with HITL |
He he... doing my best to overwhelm everyeone. |
Backport failed to create: v3-1-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 82343f6 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
Add several new filtering criteria to
breeze pr auto-triage, organized intological option groups in
pr_commands_config.py.Summary
--label 'area:*'and--exclude-label 'provider:amazon*'— exactpatterns are pushed to GitHub search, wildcards are matched client-side with fnmatch
--created-after,--created-before,--updated-after,--updated-before(YYYY-MM-DD format) — pushed directly to GitHub search qualifiers
--include-collaboratorsto include collaborator/member/owner PRs(normally skipped)
--pending-approval-onlyto only show PRs with workflow runsneeding approval, skipping all other assessment
--checks-state failure|success|pending|anyto focus on PRs with aspecific CI outcome
--min-commits-behind Nto find PRs that are at least N commits behindthe base branch
--exclude-labelto exclude PRs by label (supports wildcards)Option groups reorganized in
pr_commands_config.pyinto: Target selection,Filter options, Pagination and sorting, Assessment options, Action options.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines