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

   @KyleJamesWalker This PR has been converted to **draft** because it does not 
yet 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: **Failing CI checks**: `Postgres tests: core / 
DB-core:Postgres:14:3.10:API...CLI` is failing past the 96h grace window. Run 
the affected tests locally to reproduce: `breeze testing core-tests --backend 
postgres --test-type "API CLI"`.
   - :x: **Unresolved review comments**: There are 2 unresolved review threads 
from @kaxil. For each one: either apply the suggestion in a follow-up commit, 
or reply in-thread with a brief explanation of why the feedback doesn't apply, 
or resolve the thread if the feedback is no longer relevant. **Once you believe 
a thread is resolved — whether by pushing a fix or by explaining why the 
suggestion doesn't apply — it is the author's responsibility to mark it as 
resolved by clicking the 'Resolve conversation' button at the bottom of the 
thread.** Reviewers don't auto-close their own threads, so unresolved threads 
read as 'still waiting on the author' and block the PR from moving forward.
   
   **What to do next:**
   - Fix the failing test(s) above and verify locally.
   - Address each unresolved thread (push a fix, reply with reasoning, or 
resolve).
   - Mark the PR as "Ready for review" when you're done.
   
   Converting a PR to draft is **not** a rejection — it is an invitation to 
bring the PR up to the project's standards so that maintainer review time is 
spent productively. There is no rush — take your time and work at your own 
pace. We appreciate your contribution and are happy to wait for updates. If you 
have questions, feel free to ask on the [Airflow 
Slack](https://s.apache.org/airflow-slack).
   
   ---
   
   _Note: This comment was drafted by an AI-assisted triage tool and may 
contain mistakes. Once you have addressed the points above, an Apache Airflow 
maintainer — a real person — will take the next look at your PR. We use this 
[two-stage triage 
process](https://github.com/apache/airflow/blob/main/contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated)
 so that our maintainers' limited time is spent where it matters most: the 
conversation with you._
   


-- 
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