potiuk commented on PR #62296:
URL: https://github.com/apache/airflow/pull/62296#issuecomment-4054822084

   @Subham-KRLX This PR has been **closed because of multiple quality 
violations** — it does not meet 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: **Promotional spam / coordinated link-building**: This PR is part of a 
coordinated promotional campaign for the WFGY project 
(https://github.com/onestardao/WFGY). The linked issue #62291 was created by 
`onestardao` (the WFGY project owner), and this PR was submitted by a different 
account (`Subham-KRLX`) to fulfill it. A GitHub search reveals 127+ PRs/issues 
mentioning WFGY across multiple repositories, indicating a systematic campaign 
to insert links to this project into major open-source codebases. This is 
promotional spam disguised as documentation contributions.
   - :x: **Content does not belong in core Airflow**: RAG failure analysis is 
not a core Airflow concept — it is an external use-case pattern. The 
documentation and example DAG do not demonstrate Airflow features; they 
describe RAG/LLM concepts and serve primarily to promote the WFGY ProblemMap. 
Airflow's how-to documentation should cover Airflow features and functionality, 
not be a vehicle for third-party project promotion.
   - :x: **Low-quality AI-generated example DAG**: The example DAG 
(example_rag_dag.py) uses `random.randint()`, `random.random()`, and 
`random.uniform()` to simulate failures — it does not demonstrate any real 
Airflow functionality or actual RAG pipeline integration. It is pseudo-code 
that would never be useful to run. This is placed in 
`airflow-core/src/airflow/example_dags/`, which is reserved for demonstrating 
actual Airflow features.
   - :warning: **Coherent changes**: The spelling_wordlist.txt changes add 
domain-specific RAG/LLM terms (chunking, cosine, guardrail, hallucination, LLM, 
WFGY, ProblemMap, retriever) that are not used elsewhere in Airflow 
documentation, further indicating this content doesn't belong in the project.
   
   You are welcome to open a new PR that addresses the issues listed above. 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]

Reply via email to