SalAlba commented on pull request #10864: URL: https://github.com/apache/airflow/pull/10864#issuecomment-692273340
Eureka guys !! now I start know how the stuffs should be done, and solve open source issues (before I didn't know since I'm new to this type of project) For first time I should fork and clone the airflow repo, and make the configurations ``` git clone https://...... ``` then just onec add ref to remote official airflow repo like bellow ``` git remote add apache https://github.com/apache/airflow.git ``` then fixing issues and make life happier :smile:, when it come to commit I should do this ``` git add . git commit -m '.....' ``` then do the rebaseing like bellow ``` git fetch --all git rebase apache/master ``` in case there are conflict fix it, if there are need of pullig also do and then ``` git push ``` After all of that should come finally the `PR` From MyRepo/master -->> apache/master So my question now I'm right ? if yes should I close this current PR and open new fresh and clean `PR` for my actual issue (Increase typing coverage for postgres provider) ?? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
