@Aprillion would you be willing to create and add the PAT to the repo secrets? It can be a fine-grained PAT with only write privileges for the repo.

One other thing about this workflow is that it seems bypass branch protection rules. I set master to require a PR on my fork but was still able to run this workflow. Not a deal-breaker IMO, but something to be aware of.

oof, I had to enroll the org to allow PAT first in https://github.com/organizations/StampyAI/settings/personal-access-tokens, now I can change the Resource owner in https://github.com/settings/personal-access-tokens/new to StampyAI to be able to select this repo and generate the PAT 😓

I created one with the Contents permission with longest possible expiration (1 year) and copied it to a new repository secret PUSH_AUTH_TOKEN in https://github.com/StampyAI/stampy-ui/settings/secrets/actions

and I sent you org invitation with the Members role and Deployers team so you should be able to trigger workflows 🤞

@Aprillion sounds good, thank you 🙇