I think we have far bigger problem now. Seems that the change triggered an infinite loop of some kind and my user now is disabled from Github Actions. I pushed a change just before the policy change went live. I guess other people might have similar pro
J. Hello Jarek, I work on the Support team at GitHub, and we have some concerns about your Actions runs on the apache/airflow repository. We've noticed that there are around 30k failed Actions runs in the last hour for your potiuk user, and this has been ongoing for a few hours now. All of those runs are in the apache/airflow repository and can be seen on this page: https://github.com/apache/airflow/actions. It looks like you may have triggered an infinite loop of some kind. As a result, the repository is consuming a non-trivial amount of resources and has the potential to negatively affect the GitHub service for other users. To reduce the number of workflows being run, we've had to temporarily disable Actions for the potiuk user. We'd ask that you please take a look at what may have triggered these runs, and once it's resolved we'll be happy to work with you to turn Actions back on. Please let us know if you have any questions or concerns. Thanks, GitHub Support Thanks, Tammy GitHub Support -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
