ashb opened a new pull request #9098:
URL: https://github.com/apache/airflow/pull/9098


   scripts/ci/*.sh uses MY_DIR to mean scripts/ci, but in `breeze` MY_DIR
   is the same as AIRFLOW_SOURCES. When jumping back-and-forth between
   ci/_utils.sh, breeze, and ci/ci_*.sh it can be confusing to keep track
   of what is what.
   
   This changes `breeze` to use `AIRFLOW_SOURCES` to referrer to the top
   level folder instead -- that means I don't have to keep as much context
   in my head
   
   In doing this I noticed a small "bug" -- we were creating ./scripts/ci/.kube
   folder
   
   ---
   Make sure to mark the boxes below before creating PR: [x]
   
   - [x] Description above provides context of the change
   - [x] Unit tests coverage for changes (not needed for documentation changes)
   - [x] Target Github ISSUE in description if exists
   - [x] Commits follow "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)"
   - [x] Relevant documentation is updated including usage instructions.
   - [x] I will engage committers as explained in [Contribution Workflow 
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   ---
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   Read the [Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)
 for more information.


----------------------------------------------------------------
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]


Reply via email to