1fanwang commented on issue #66793: URL: https://github.com/apache/airflow/issues/66793#issuecomment-4472961003
Thanks for the nudge and context @potiuk, Apologies for the noise I was used to a certain workflow where 1. a Jira Ticket (similar to a GH issue) created for tracking / share context / define Acceptance Criteria - essentially to tell the Problem, to define the "Why" 2. then have PR for implementation, and solution, which focuses on the "What" Reading this msg and the guidelines I see the Airflow OSS community prefers PR directly, which also makes sense, just opening the PRs with the full context works just as well. Will make sure to follow that in the future. Also quick question do you want me to close the issues where I've made these noisy mistakes? or is this just noting for the future, lemme know, happy to follow your suggestion either ways. 🙌 -- 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]
