Losita/mai-bot
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

hotfix:fix workflow

Browse Source
This commit is contained in:
Losita
2026-05-11 20:36:54 +08:00
parent 7ebc9e11ea
commit 2bc1b42be9
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
deploy/server-maibot/README_DEPLOY_STEPS.txt
View File

@@ -21,7 +21,7 @@ Gitea workflow:
- .gitea/workflows/release-offline.yml
Current pipeline mode:
- single-host release on the repo-level `build-host` runner
- release on a runner that exposes the default `ubuntu-latest` label
- fetches the source commit from the workflow repository itself
- defaults to `${gitea.server_url}/${gitea.repository}.git`
- can override the clone URL with the repository variable `MAIBOT_REPO_URL`
@@ -39,6 +39,8 @@ Optional environment overrides for the workflow runtime:
- `MAIBOT_BASE_IMAGE`
Runner connectivity note:
- the runner must advertise the `ubuntu-latest` label; this is part of the default Gitea runner label set unless you replaced it during registration
- if your production runner only has custom labels, either add `ubuntu-latest` back on the runner side or change the workflow label to your actual runner label
- if the runner cannot access `${gitea.server_url}` directly, set `MAIBOT_REPO_URL` to a runner-reachable HTTPS clone URL
- for private repositories, the workflow uses the built-in `GITEA_TOKEN`, so no extra personal access token secret is needed
- the repository or owner Actions settings must allow the job token to read repository contents