I hadn't meant to add the potential action to main to begin with, but in trying to make the manual trigger for the github action appear on my test branch, I accidentally put the draft file on main instead. After digging into a bunch of permissions issues, from the pull_request action it seems:
These restrictions mean that during a pull_request event triggered by a forked repository, actions have no write access to GitHub resources and will fail on any attempt.
So essentially, built in limitations mean that we can't have an action triggered from a fork of a template that will open a PR to update the template.
No worries, I think i temporarily disabled the branch protection to avoid pushes directly to main when working out the tutorial reorganization. just reenabled it to be sure.
I hadn't meant to add the potential action to main to begin with, but in trying to make the manual trigger for the github action appear on my test branch, I accidentally put the draft file on main instead. After digging into a bunch of permissions issues, from the
pull_request
action it seems:So essentially, built in limitations mean that we can't have an action triggered from a fork of a template that will open a PR to update the template.