Skip to content

Commit a1d69bb

Browse files
committed
docs: note the tag job's workflow-scope limit
1 parent ff4ecbb commit a1d69bb

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

‎README.md‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,11 @@ When a step fails:
5454
`main`, not the merge commit. Until the version is tagged, the next proposal fails, so no version is proposed twice.
5555
When the error says the version has no tag and no merged pull request was found, GitHub had not listed the release
5656
merge yet. Re-run the run once the pull request shows as merged, or dispatch the workflow on `main` while the merge
57-
commit is still its newest commit. A direct push of an untagged version fails the same way.
57+
commit is still its newest commit. A direct push of an untagged version fails the same way. The job creates the tag
58+
with a token that has contents write only, and GitHub refuses a ref at a commit whose `.github/workflows` tree
59+
matches no branch tip unless the token has workflow scope. So re-run a failed `tag` job before any workflow change
60+
lands on `main`. If one already has, a maintainer creates the tag by hand and pushes it over SSH. The tag's push runs
61+
the release workflow, as a dispatch would only run a dry run.
5862
* The release workflow's `downstream` job failed: the release is published, so don't re-run the release run. Run
5963
`generator.yml` in tibia-sh/tibiawiki-mcp by hand with the version.
6064

0 commit comments

Comments
 (0)