potiuk commented on PR #62296: URL: https://github.com/apache/airflow/pull/62296#issuecomment-4038914726
@Subham-KRLX This PR has a few issues that need to be addressed before it can be reviewed — please see our [Pull Request quality criteria](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-quality-criteria). **Issues found:** - :x: **Gen-AI disclosure**: The PR description contains no generative-AI disclosure checkbox or statement, yet the contribution exhibits strong AI-generated content signals: the 'WFGY 16-problem framework' is not a recognised industry standard for RAG debugging and appears to be a hallucinated/fabricated reference; the 'Semantic Firewall' label for a simulated pipeline task is non-standard jargon commonly produced by LLM tools. Per the project's contributing guidelines, any PR co-authored with gen-AI tools must include an explicit disclosure. - :x: **AI-generated code signals**: The cited 'WFGY 16-problem framework' does not correspond to any known, publicly documented RAG evaluation or debugging framework. Referencing a non-existent or AI-hallucinated external standard in official Airflow documentation is a concrete signal of low-quality, unreviewed AI-generated content being submitted without the author verifying the factual claims. - :warning: **Coherent changes / scope**: Apache Airflow is a general-purpose workflow orchestrator. Adding a documentation guide and example DAG specifically centred on RAG (Retrieval-Augmented Generation) LLM pipeline failure modes is outside the scope of Airflow's core documentation. This content would belong in a provider package, an external tutorial, or a dedicated ML-ops guide, not in the main how-to section of the Airflow docs. > **Note:** Your branch is **157 commits behind `main`**. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results. **What to do next:** - The comment informs you what you need to do. - Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed. - Maintainers will then proceed with a normal review. Please address the issues above and push again. If you have questions, feel free to ask on the [Airflow Slack](https://s.apache.org/airflow-slack). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
