You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "YAshhh29 (via GitHub)" <gi...@apache.org> on 2026/07/26 18:47:32 UTC
[PR] Make generated AIP playbooks portable and verifiable [airflow]
YAshhh29 opened a new pull request, #70477:
URL: https://github.com/apache/airflow/pull/70477
The `aip-user-stories` skill is shared across agent runtimes, but its generated output currently targets a Claude-specific directory. Its verification workflow also assumes implementation code lives under `airflow-core`, which can miss features implemented in distributions such as `airflow-ctl`.
This change makes generated playbooks portable and strengthens the existing verification promise by:
- writing playbooks to Airflow's vendor-neutral `files/` output directory
- distinguishing pasted AIP content from local file arguments
- discovering implementation and package metadata across workspace distributions
- requiring evidence for Verified, Adapted, and Unverified code examples
- avoiding unsupported release-version claims
- validating evidence, imports, prerequisites, and implementation status before writing
The bundled playbook template now records release availability, required packages, runtime prerequisites, verification tier, and repository evidence.
Validation:
- `prek run check-merge-conflict --files ...`
- `prek run end-of-file-fixer --files ...`
- `prek run trailing-whitespace --files ...`
- `prek run lint-markdown --files ...`
- focused assertions for the skill's input, package discovery, evidence, validation, and output contracts
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — GitHub Copilot
Generated-by: GitHub Copilot following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
Drafted-by: GitHub Copilot (no human review before posting)
--
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] Make generated AIP playbooks portable and verifiable [airflow]
Posted by "YAshhh29 (via GitHub)" <gi...@apache.org>.
YAshhh29 commented on PR #70477:
URL: https://github.com/apache/airflow/pull/70477#issuecomment-5264652406
Friendly review-queue bump: this PR is labeled `ready for maintainer review`, all checks are green, and it has not yet received a human review. The change is limited to the `aip-user-stories` skill and its documentation and validation workflow.
Is there anything else needed from me before a maintainer can take a first pass?
Drafted-by: GitHub Copilot; reviewed by @YAshhh29 before posting
---
--
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] Make generated AIP playbooks portable and verifiable [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk closed pull request #70477: Make generated AIP playbooks portable and verifiable
URL: https://github.com/apache/airflow/pull/70477
--
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] Make generated AIP playbooks portable and verifiable [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #70477:
URL: https://github.com/apache/airflow/pull/70477#issuecomment-5839410128
Hello @YAshhh29 - thank you for your contributions to Apache Airflow!
The Airflow community has introduced a limit of **5 open pull requests at a time** for contributors without write access to the repository. You currently have 6 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
* #69385 - Make Vertex AI evaluation stack an opt-in provider extra
* #69673 - Add QdrantSearchOperator for vector similarity search
* #70477 - Make generated AIP playbooks portable and verifiable
* #71101 - Fix upstream failure branch in task lifecycle diagram
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
* #69812 - Support Pydantic structured outputs in OpenAIResponseOperator
* #71575 - Do not replay cached AI steps that cannot be verified
This is **not** a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are.
What we ask you to do is to make your **first prioritization decision**: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or `gh pr reopen <PR_NUMBER> --repo apache/airflow`. Reopen the ones you are ready to follow through - keep them rebased, respond to review comments and fix failing checks.
While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack.
Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst.
---
Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting
--
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