syntaqxThe Actions release pushes with its publish token alone. actions/checkout left the job's own token in git's config for g1t.sh, so each push sent it beside the publish token, and g1t took the job's, which may only write this repository: the release created g1t/deploy and was then refused pushing to it. The checkout keeps no credentials now.ac8b3daHistory
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml