larvit/smpp-js
3
0
Fork 0
Code Issues Pull Requests Actions Activity

Say what the mirror's concurrency group does, and name every way a stale ref survives
Test / lint (pull_request) Successful in 20s
Details
Test / test (26) (pull_request) Successful in 17s
Details
Mirror / push (push) Successful in 3s
Details
Test / test (18) (pull_request) Successful in 18s
Details
Test / test (20) (pull_request) Successful in 18s
Details
Test / test (22) (pull_request) Successful in 18s
Details
Test / test (24) (pull_request) Successful in 17s
Details

Browse Source
This commit was merged in pull request #5.
This commit is contained in:
Lilleman auf Larv
2026-09-14 20:54:04 +02:00
parent 14b114afda
commit c5adfd8e39
3 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+3 -3
View File
@@ -148,9 +148,9 @@ docker compose run --rm node npm run build
TypeScript 7 once that constraint lifts.
- GitHub mirrors Gitea through `.gitea/workflows/mirror.yaml`, which never prunes, and
`mirror-delete.yaml`, one run per deleted ref. A delete run that fails or outlives Gitea's queue
timeout leaves the ref on GitHub until it is re-run. Accepted: a stale ref there is harmless, and
refs only GitHub has must survive. Maintainer's call, 2026-09-14; valid while nothing deploys from
GitHub.
timeout, or a push run that cloned before the delete, leaves the ref on GitHub until the delete
run is re-run. Accepted: a stale ref there is harmless, and refs only GitHub has must survive.
Maintainer's call, 2026-09-14; valid while nothing deploys from GitHub.
## Defects found in 0.4.0