fix(ci): use PAT instead of GITHUB_TOKEN for tag push to trigger tag.yaml #9
Reference in New Issue
Block a user
Delete Branch "fix/use-pat-for-tag-push"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problème
Le job
tagdansmain.yamlpousse les tags viaGITHUB_TOKEN(le token interne Gitea Actions). Par design, les pushes faits avec ce token ne déclenchent pas de nouveaux workflows — c'est ce qui empêchetag.yamlde se lancer après la création d'un tag.Cf. issue Gitea #33123 — "gitea-actions user does not trigger workflows to prevent an endless cycle."
Solution
Remplacer
GITHUB_TOKENpar un Personal Access Token (SA_TOKEN_ACTION_PUSH_TAGS) stocké comme secret org. Un vrai PAT de l'utilisateurjcabillotdéclenche correctement les webhooks →tag.yamlsera lancé.Changements
.gitea/workflows/main.yaml— jobtag:secrets.GITHUB_TOKEN→secrets.SA_TOKEN_ACTION_PUSH_TAGSdans l'URLgit remotesecrets.GITHUB_TOKEN→secrets.SA_TOKEN_ACTION_PUSH_TAGSdans l'env deanothrNick/github-tag-action