Closed ChrisMarsh82 closed 8 months ago
Merging without review in order to test actions
I think you can probably just add a branch push trigger to test actions on push to the branch under development instead of merging into master.
Generally preferred as master deployment has a couple of side-effects associated with it, such as redeploying the hosting sites, and allows for code review
Also, just to check - is this so that deployment repos don't have to store their own github actions? Makes a lot of sense, but I'm wondering if this means we should also be removing the current templating system we have to add actions to a repo?
I'm guessing this was discussed on a call I wasn't on and I'm just out the loop a bit, been a bit confused now coming to review some of the PRs that build on top of this
Description
Added actions to be called from content repositories. All actions must inherit secrets from repos that run the actions.