FYI - I started to get notifications from GitHub that the workflows I had in the airflow forks are being disabled, so it happens as planned !
On Wed, Oct 28, 2020 at 2:18 PM Jarek Potiuk <jarek.pot...@polidea.com> wrote: > Hello everyone, > > We had protection in Airflow GitHub actions that prevented our scheduled > workflows (mostly cleanup and maintenance) to run in forks. We are going to > disable the protection in this PR today unless someone objects: > https://github.com/apache/airflow/pull/11876 > > Following information from GitHub we received, it is no longer needed as > of yesterday because both new and all forks have the scheduled workflows > disabled unless the user explicitly allows them. > > For some reason this information is not public in GitHub documentation, it > was only sent via email (or at least I could not find it), so I am > forwarding it to the devlist for reference. > > J. > > ---------- Forwarded message --------- > From: GitHub <no-re...@github.com> > Date: Thu, Oct 1, 2020 at 9:31 PM > Subject: Updates to GitHub Actions usage policy: scheduled workflows in > inactive and forked public repositories. > To: <ja...@potiuk.com> > > > Scheduled workflows will be disabled by default in forks of public repos > and in public repos with no activity for 60 consecutive days. > [image: GitHub] > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=eaed836ef9&e=1d97945941> > Scheduled workflows will be disabled by default in forks of public repos > and in public repos with no activity for 60 consecutive days. > > We’re making two changes to the usage policy for GitHub Actions. These > changes will enable GitHub Actions to scale with the incredible adoption > we’ve seen from the GitHub community. Here’s a quick overview: > > - Starting today, scheduled workflows will be disabled by default in > new forks of public repositories. > - Scheduled workflows will be disabled in public repos with no activity > > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=9a9b5954e8&e=1d97945941> > for 60 consecutive days. > > We’re dedicated to helping the open source community be productive, which > is why GitHub Actions is free for the 50 million developers who work with > public repositories. These changes will help us ensure a great GitHub > Actions experience for the next 50 million developers on GitHub. > > To further evaluate how this will affect you, please read our FAQ below > and contact GitHub Support > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=ed75d3188f&e=1d97945941> > if you run into any problems or need help. You can also always get up to > date information about our usage policies in our Docs > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=1ddfd18f6c&e=1d97945941>. > > > Thank you for using GitHub Actions 💙 > ------------------------------ > > *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. > > *I have inactive public repos, are my scheduled workflows being disabled?* > We are not evaluating public repos for 60 consecutive days of inactivity > until October 27, 2020. After that, public repos with 60 consecutive days > of inactivity will have scheduled workflows disabled. Inactive repo owners > will receive a reminder email 7 days before any workflows are disabled and > can choose to keep them running at that time. > > *Can I re-enable disabled workflows?* > Yes! You can easily re-enable any workflow that has been disabled by using > the brand new feature to enable & disable workflows. You can enable a > disabled workflow with a few clicks. > ------------------------------ > > Unsubscribe > <https://github.us11.list-manage.com/unsubscribe?u=9d7ced8c4bbd6c2f238673f0f&id=706e2a5948&e=1d97945941&c=37fe4f90aa> > · Email preferences > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=45534efa2c&e=1d97945941> > · Terms > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=9a17c09fc4&e=1d97945941> > · Privacy > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=12a99ad7ca&e=1d97945941> > · Sign in to GitHub > <https://github.us11.list-manage.com/track/click?u=9d7ced8c4bbd6c2f238673f0f&id=e88a4dda9f&e=1d97945941> > > GitHub, Inc. > 88 Colin P Kelly Jr St. > San Francisco, CA 94107 > > > -- > +48 660 796 129 > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > [image: Polidea] <https://www.polidea.com/> > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
