Fix documented Breeze selective checks command#69861
Conversation
|
Sorry I don't have Claude 😭 |
|
Hi! I have regenerated the hash for you. You can simply paste it to |
Contributor instructions currently point to a nonexistent Breeze command, preventing developers and coding agents from reproducing selective CI decisions locally. Signed-off-by: viiccwen <vicwen@apache.org>
8877930 to
ff4cbd3
Compare
Thx for your kindness. 🫡 |
|
Thanks, really helpful 😄 |
|
Thanks for the fix, and sorry the eval-hash gate (from #69308) added friction here. I'm experimenting with additional agent runtimes for the eval (Codex and OpenCode SDKs)and will propose that in a follow-up PR, so the gate won't assume a Claude subscription. 🙌 |
Nice! |
There was a problem hiding this comment.
Thanks for the catch.
Additionally, this is exactly what #64012 would like to prevent from happening -- we should introduce an automated mechanism to prevent further drift instead of relying on manual catch.
Backport failed to create: v3-3-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 d9dcc11 v3-3-testThis should apply the commit to the v3-3-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. |
|
I was curious what a wrong documented command like this actually costs an agent in tokens, so I ran this fix through the skill-eval harness (#69308) as a before/after A/B — same task ("determine which CI test types run for HEAD"), same tools, only AGENTS.md differs, n=3 per arm:
Every "before" run trusted the doc, failed, and had to rediscover |
|
@jason810496 Agreed! #68204 only keeps docs and AGENTS.md in sync, the bug was in the docs source, so the sync faithfully copied it over. Nothing checks that the commands are actually real. Working on that now: validate documented commands against the real Breeze CLI, both when docs are generated and when a command gets renamed. |

closes #69858
Correct the contributor documentation to use
breeze ci selective-check, which is the command registered by Breeze and executed by the GitHub Actions workflows.This updates the source
AGENT-SKILLcommand block, regenerates the Commands section inAGENTS.md, fixes the local reproduction example in the selective checks troubleshooting guide, and adjusts the generator test to verify the valid command.Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.