title: Efficient way to deploy dag files on airflow
body: <p>Are there any best practices that are followed for deploying new dags to airflow? </p>
  
  <p>I saw a couple of comments on the google forum stating that the dags are saved inside a GIT repository and the same is synced periodically to the local location in the airflow cluster.<br>    Regarding this approach, I had a  couple of questions
  <li>
    Do we maintain separate dag files for separate environments? (testing. production)
    <li>How to handle rollback of an ETL to an older version in case the new version has a bug?</p>
  
  <p>Any help here is highly appreciated. Let me know in case you need any further details?</p>