You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/04/03 10:48:53 UTC
[PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
potiuk opened a new pull request, #64667:
URL: https://github.com/apache/airflow/pull/64667
Add a new `breeze pr stats` command that produces aggregate statistics of open PRs in the Airflow repo, split by area label. The command uses GraphQL to fetch all open PRs and displays two tables:
1. **Triaged PRs — Final State**: Shows triaged PRs that were closed or merged since 2026-03-11, with counts and percentages for closed, merged, and author-responded.
2. **Triaged PRs — Still Open**: Shows all open PRs grouped by area with draft/non-draft counts, contributor counts, triage status, response rates, ready-for-review status, time since triager drafted the PR, and time since the author's last interaction.
Features:
- Cached interaction data (keyed by updated_at) to avoid re-fetching unchanged PRs on subsequent runs
- `--clear-cache` flag to force fresh data
- Detects triager draft conversions via GraphQL timeline events
- Tracks closed vs merged triaged PRs with area breakdown
- Footer header rows on both tables for readability
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull request.
Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the documentation.
Feel free to ping (in general) for the review if you do not see reaction for a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR, please
change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #64667:
URL: https://github.com/apache/airflow/pull/64667#issuecomment-4185266082
### Backport failed to create: v3-2-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/23962805724'> Run details </a>
Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
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](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.
<table>
<tr>
<th>Status</th>
<th>Branch</th>
<th>Result</th>
</tr>
<tr>
<td>❌</td>
<td>v3-2-test</td>
<td><a href="https://github.com/apache/airflow/commit/8c4c9908b8ca7c9fac0faf2b1b94bf58ae389576"><img src='https://img.shields.io/badge/Commit-8c4c990-red' alt='Commit Link'></a></td>
</tr>
</table>
You can attempt to backport this manually by running:
```bash
cherry_picker 8c4c990 v3-2-test
```
This should apply the commit to the v3-2-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:
```bash
cherry_picker --continue
```
If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-cherry-picker-cli).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "bugraoz93 (via GitHub)" <gi...@apache.org>.
bugraoz93 commented on code in PR #64667:
URL: https://github.com/apache/airflow/pull/64667#discussion_r3034252213
##########
uv.lock:
##########
Review Comment:
This could mean there is a problem or discrepancy.
Normally, that shouldn't happen. We are keeping uv.lock for a couple of reasons. For examle recently cool down added to upgrade process and uv.lock manages reproducibility over cool down period and there are many more things.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #64667:
URL: https://github.com/apache/airflow/pull/64667
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "shivaam (via GitHub)" <gi...@apache.org>.
shivaam commented on code in PR #64667:
URL: https://github.com/apache/airflow/pull/64667#discussion_r3033728545
##########
uv.lock:
##########
Review Comment:
recently been seeing uv.lock updating every time I am running tests locally. I think we can add it to .gitignore as I have been just excluding it from commits
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #64667:
URL: https://github.com/apache/airflow/pull/64667#discussion_r3034515817
##########
uv.lock:
##########
Review Comment:
Possibly that one shoudl help https://github.com/apache/airflow/pull/64699 - however uv.lock will change whenever you add a new dependency - and this is **absolutely** expected.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "jscheffl (via GitHub)" <gi...@apache.org>.
jscheffl commented on code in PR #64667:
URL: https://github.com/apache/airflow/pull/64667#discussion_r3033506374
##########
uv.lock:
##########
Review Comment:
Why is UV Lock updated in this PR?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Add `breeze pr stats` command for open PR statistics by area [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #64667:
URL: https://github.com/apache/airflow/pull/64667#discussion_r3034444539
##########
uv.lock:
##########
Review Comment:
uv.lock gets updated because the time moves - so cooldown is still used and whenever `uv sync` is run, the time changes in the `uv.lock` and potentially new dependencies (that reached the 4 day threshold are added)
So there is nothing **wrong** with the uv.lock change - but I think it is far too noisy and conflict-prone. So we need to solve it differently.
We **cannot** add it to .gitignore, because the whole point is to keep it in the repo to sync everyone to the same version. I will look to that.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org