potiuk commented on PR #64189: URL: https://github.com/apache/airflow/pull/64189#issuecomment-4169565248
@MFWhen 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: **Meaningful description**: The PR body contains no meaningful description of what the bug is, what the root cause is, or why these specific code changes fix it. The body is entirely the unfilled PR template — only the Gen-AI checkbox was touched; the actual description area above the '---' separator is completely blank. - :x: **Unresolved merge conflict markers**: The file airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts contains unresolved Git merge conflict markers (<<<<<<< HEAD, =======, >>>>>>> 4bce21a34c62fcdb5b920d6c7535a6f9684cf079) inside the navigateToCalendar method. The file is broken and cannot be compiled or run as submitted. - :x: **Gen-AI disclosure**: The author checked the Gen-AI box but left the tool name as the template placeholder '(please specify the tool below)' without naming the actual tool. The 'Generated-by' line is still commented out with '[Tool Name]' unfilled. The disclosure is incomplete per project guidelines. - :warning: **Coherent changes**: dev/update_github_branch_config.py is included with a file-mode change (100755 → 100644) that is completely unrelated to any DagCalendarTab fix. Unrelated changes should be removed before submitting for review. **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. - There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. - Maintainers will then proceed with a normal review. 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). -- 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]
