[GitHub] BasPH commented on issue #4370: [AIRFLOW-3459] Move DagPickle to separate file
BasPH commented on issue #4370: [AIRFLOW-3459] Move DagPickle to separate file URL: https://github.com/apache/incubator-airflow/pull/4370#issuecomment-450821127 The contributing guide states to squash all commits into a single commit yourself with message like `[AIRFLOW-XXX] ...`, so you're saying that's not needed? If so, I could update the contributing guide. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] BasPH commented on issue #4370: [AIRFLOW-3459] Move DagPickle to separate file
BasPH commented on issue #4370: [AIRFLOW-3459] Move DagPickle to separate file URL: https://github.com/apache/incubator-airflow/pull/4370#issuecomment-450035982 This page describes the exact same thing I experienced: https://github.com/isaacs/github/issues/361. Doesn't sound like something that can be configured from the repository end. However, I think squashing commits by the Airflow committers would help prevent lots of force pushes. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] BasPH commented on issue #4370: [AIRFLOW-3459] Move DagPickle to separate file
BasPH commented on issue #4370: [AIRFLOW-3459] Move DagPickle to separate file URL: https://github.com/apache/incubator-airflow/pull/4370#issuecomment-450018524 Spotted a mistake in my code, closed the issue to fix it first, then discovered I couldn't re-open because I done a force push... when will the Airflow project change its contributing policy? ;) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
