docs: WDIPL-Runner act cache + pin uses to SHA
Made-with: Cursor
This commit is contained in:
15
readme.md
15
readme.md
@@ -25,6 +25,7 @@ on:
|
||||
|
||||
jobs:
|
||||
ci:
|
||||
# Prefer a commit SHA from wdipl-actions @main (see "stale reusable workflows" above).
|
||||
uses: http://git.wdipl.com/Rajendra.Reddy/wdipl-actions/.gitea/workflows/ci.yml@main
|
||||
|
||||
with:
|
||||
@@ -153,6 +154,20 @@ pm2 reload <pm2_id>
|
||||
|
||||
---
|
||||
|
||||
# WDIPL-Runner: stale reusable workflows (`uses: ...@main`)
|
||||
|
||||
The runner caches clones under **`/root/.cache/act/`** (e.g. `Rajendra.Reddy-wdipl-actions@main`). After you change **`wdipl-actions`**, consumers may still execute an **old `ci.yml`** (wrong `if:` / missing `ci_steps`).
|
||||
|
||||
**Fix one of:**
|
||||
|
||||
1. Pin **`uses:` to a commit SHA** from `wdipl-actions`, e.g.
|
||||
`uses: .../ci.yml@6b9982def7d49842c0dc75529c0f60cc74a841c1`
|
||||
Bump the SHA whenever you change central CI.
|
||||
2. On the runner host, delete that cache folder and re-run the workflow.
|
||||
3. Upgrade the runner if a newer release fixes cache invalidation.
|
||||
|
||||
---
|
||||
|
||||
# Gitea MCP + Actions API (Cursor)
|
||||
|
||||
Official **gitea-mcp** (and the Go SDK it uses) calls **`GET /api/v1/repos/{owner}/{repo}/actions/runs`** to list workflow runs and job logs.
|
||||
|
||||
Reference in New Issue
Block a user