Hi Ash, In the contributors' docs, we guide users to use `breeze ci audit` to check whether their fork's CI environment is set up correctly. Docs: https://github.com/apache/airflow/blob/main/contributing-docs/18_contribution_workflow.rst#ci-in-your-fork
> I do wonder if other people with existing forks might also have “Disable actions” set? Yes, I also ran into this when testing as a pilot. So I've made some changes to help this command detect settings that could block CI. I think one problem is that the bot's comment on the PR could guide users to this doc earlier. Currently it guides users to the fork CI design doc instead, which is not easy to read and has no quick setup steps to follow. Thanks, Andrew
