Skip to content

Commit

The 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.

syntaqxcommitted Parentcfaf5efBrowse files
1 file+5−00/1 viewed
+5−0
5959 - uses: actions/checkout@v5
6060 with:
6161 fetch-depth: 0
62+ # Without the job's own token left in git's config: it would go
63+ # with every request to g1t.sh, beside the publish token below,
64+ # and git sends the first, which may only write this repository,
65+ # so the pushes to g1t/<name> were refused (403).
66+ persist-credentials: false
6267 - name: Push each action and move its major tag
6368 env:
6469 PUBLISH_TOKEN: ${{ secrets.ACTIONS_PUBLISH_TOKEN }}