potiuk opened a new pull request #11876:
URL: https://github.com/apache/airflow/pull/11876
GitHub Actions policy about runnig scheduled workflows in forks
has changed recently and as of October 27 2020 scheduled workflows
in forks will be disabled. Thanks to that change we can simplify
some of our conditions that disallowed running scheduled workflows
in forks.
The change is active as of today (email from GitHub):
> What will happen to scheduled workflows in forks I already have?
> If you already have scheduled workflows in forks of public
repositories, they will be disabled on October 27, 2020. Repository
owners will receive a reminder email 7 days prior and can choose to
keep the workflows running at that time if they are needed.
<!--
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]
