Skip to content

Add filtering options to auto-triage command#63300

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:add-auto-triage-filter-options
Mar 10, 2026
Merged

Add filtering options to auto-triage command#63300
potiuk merged 1 commit intoapache:mainfrom
potiuk:add-auto-triage-filter-options

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Mar 10, 2026

Add several new filtering criteria to breeze pr auto-triage, organized into
logical option groups in pr_commands_config.py.

Summary

  • Wildcard labels: --label 'area:*' and --exclude-label 'provider:amazon*' — exact
    patterns are pushed to GitHub search, wildcards are matched client-side with fnmatch
  • Date filters: --created-after, --created-before, --updated-after, --updated-before
    (YYYY-MM-DD format) — pushed directly to GitHub search qualifiers
  • Collaborator toggle: --include-collaborators to include collaborator/member/owner PRs
    (normally skipped)
  • Pending approval mode: --pending-approval-only to only show PRs with workflow runs
    needing approval, skipping all other assessment
  • CI state filter: --checks-state failure|success|pending|any to focus on PRs with a
    specific CI outcome
  • Staleness filter: --min-commits-behind N to find PRs that are at least N commits behind
    the base branch
  • Label exclusion: --exclude-label to exclude PRs by label (supports wildcards)

Option groups reorganized in pr_commands_config.py into: Target selection,
Filter options, Pagination and sorting, Assessment options, Action options.


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6) following the guidelines

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>
Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starting to get owverwhelmed with options now :-D Do I need a LLM to start using all the options? :-D

@gopidesupavan
Copy link
Member

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

@potiuk
Copy link
Member Author

potiuk commented Mar 10, 2026

Starting to get owverwhelmed with options now :-D Do I need a LLM to start using all the options? :-D

He he... doing my best to overwhelm everyeone.

@potiuk potiuk merged commit 82343f6 into apache:main Mar 10, 2026
131 of 132 checks passed
@potiuk potiuk deleted the add-auto-triage-filter-options branch March 10, 2026 22:39
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 82343f6 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants