TobKed opened a new pull request #9998:
URL: https://github.com/apache/airflow/pull/9998


   I found there is typo in setting environment `GITHUB_REPOSITORY` variable 
for two jobs, however jobs work fine anyway.
   After short investigation i found info 
[here](https://github.community/t/override-repository-env-var/18440/2) which 
says that:
   
   > The " GITHUB_REPOSITORY" is a default environment variable set by GitHub. 
When you try using the " env" key or the " set-env" command to change the value 
of a default environment variable, GitHub will prevent the value from being 
changed on the system, but this environment variable will be added into the  
env context with the new value.
   
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   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).
   


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