[GH-ISSUE #864] infra: CI for docker-publish does not trigger on tag #12237

New Issue

GiteaMirror · 2026-04-19T19:06:52-05:00

GiteaMirror commented

2026-04-19 19:06:52 -05:00

Originally created by @duhow on GitHub (Feb 23, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/864

b1fa32c5d6/.github/workflows/build-release.yml (L32)

🐞 This is a limitation on GitHub. You'll need to switch to a PAT to publish the tag, or use the Workflow docker-publish as a reusable workflow in another Job within the same Workflow.

Unfortunately, there's no workaround to trigger a new workflow run from within another workflow without using a personal access token or a GitHub App installation token. This is a limitation put in place by GitHub to prevent recursive workflow runs.

Events triggered by the GITHUB_TOKEN, which is automatically created for each workflow run, will not create new workflow runs. This includes pushing tags or creating releases with the GITHUB_TOKEN.

If you want to avoid using a personal access token, you might need to reconsider your workflow design. For example, you could combine the steps of your two workflows into one single workflow if possible. This way, you won't need to trigger a new workflow from within another workflow.

Originally created by @duhow on GitHub (Feb 23, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/864 https://github.com/open-webui/open-webui/blob/b1fa32c5d66eb918c4b102d34a990b982f011f70/.github/workflows/build-release.yml#L32 🐞 This is a limitation on GitHub. You'll need to switch to a PAT to publish the `tag`, or `use` the Workflow `docker-publish` as a reusable workflow in another Job within the same Workflow. > Unfortunately, there's no workaround to trigger a new workflow run from within another workflow without using a personal access token or a GitHub App installation token. This is a limitation put in place by GitHub to prevent recursive workflow runs. > > Events triggered by the GITHUB_TOKEN, which is automatically created for each workflow run, will not create new workflow runs. This includes pushing tags or creating releases with the GITHUB_TOKEN. > > If you want to avoid using a personal access token, you might need to reconsider your workflow design. For example, you could combine the steps of your two workflows into one single workflow if possible. This way, you won't need to trigger a new workflow from within another workflow.

GiteaMirror closed this issue

2026-04-19 19:06:53 -05:00

GiteaMirror commented

2026-04-19 19:06:55 -05:00

@justinh-rahb commented on GitHub (Feb 23, 2024):

We're aware of the issue and have been discussing it on the Discord, thanks! 🙏

@justinh-rahb commented on GitHub (Feb 23, 2024): We're aware of the issue and have been discussing it on the Discord, thanks! 🙏

GiteaMirror commented

2026-04-19 19:06:55 -05:00

@tjbck commented on GitHub (Mar 3, 2024):

Closing in favour of #878

@tjbck commented on GitHub (Mar 3, 2024): Closing in favour of #878

GiteaMirror referenced this issue

2026-04-19 22:25:29 -05:00

[GH-ISSUE #12237] feat: Add an option to API GET /api/v1/files/ to not return file content #16521

GiteaMirror referenced this issue

2026-04-20 04:29:09 -05:00

[PR #12431] [MERGED] feat: Allow making content optional when listing all files #22911

GiteaMirror referenced this issue