emilymye commented on pull request #12222: URL: https://github.com/apache/beam/pull/12222#issuecomment-657909594
I'm sure @TobKed knows more about Github actions than I do, but it seems there isn't a common convention. Based on the docs [docs](https://docs.github.com/en/actions/getting-started-with-github-actions/about-github-actions) and some [issues](https://github.community/t/how-to-run-and-enable-github-actions-on-forked-repo-with-github-api/17232), it seems like GH used to disable actions for forked repos by default but have since changed it. My ideal workflow is that GH itself disables actions for a forked repo and asks if the fork owner wants to re-enable the actions as shown in the example issue. @TobKed do you know if that's a configuration step when setting up actions? Otherwise, I'm fine on closing this PR and waiting for GH to provide a better way to opt-out/opt-in if we can avoid these repo-owner-specific ifs and have a better opt-in flow. ---------------------------------------------------------------- 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]
