Hello, Q re the GH action workflows. Looking at th...
# github-actions
s
Hello, Q re the GH action workflows. Looking at the workflow triggers: event based, scheduled, and manual(workflow_dispatch), noticed that scheduled and manual based triggers have a requirement that the workflow file is on the default branch which makes its development comply with the branch protection rules(require approvals, etc). But from the looks of it, it isn't the case with event based triggers. Just thinking about the security implications. Thinking of a scenario where folks can create a branch "x" and setup a workflow with a trigger on push to branch "x", and the workflow can access the repo secrets and the underlying runners ie you can trigger workflow from arbitrary branches, and can have unreviewed code running arbitrary releases. To add, the above is in reference to a private repo with GH Team license. wanted to check if i am missing anything, or if there is a workaround for the above issue, or if there is a repo/org level setting that should just do the trick.
g
@Igor Rodionov