forgejo/runner-dm
Watch
0
0
Fork
You've already forked runner-dm
 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions
No description
3 commits 1 branch 1 tag 15 KiB
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Julian Schlarb 707dd1a4ad
Some checks failed
build / build (push) Failing after 1m6s
Details
ci: drop mirror token, release as upstream tag
2026-09-29 20:10:11 +00:00
.forgejo/workflows ci: drop mirror token, release as upstream tag 2026-09-29 20:10:11 +00:00
patches feat: forgejo-runner with DenktMit patches, built via renovate 2026-09-29 19:46:39 +00:00
.gitignore feat: forgejo-runner with DenktMit patches, built via renovate 2026-09-29 19:46:39 +00:00
README.md ci: drop mirror token, release as upstream tag 2026-09-29 20:10:11 +00:00
renovate.json feat: forgejo-runner with DenktMit patches, built via renovate 2026-09-29 19:46:39 +00:00

README.md

runner-dm

forgejo-runner with the DenktMit patches. Every release v<upstream> carries the static binary forgejo-runner-<version>-dm-linux-amd64 and its .sha256, named like upstream's assets. The runner images install it from here.

Patches (patches/):

  • 0001 starts services: for jobs on :host labels, like the GitHub runner. The job reaches them via their published ports (ports: ["5432:5432"] → localhost:5432). Upstream ignores services on host labels without a warning.

How it runs

Renovate bumps UPSTREAM_VERSION in .forgejo/workflows/build.yml to the newest tag of the mirror forgejo/runner. The workflow applies the patches, runs the service tests and builds the binary. It runs on every pull request and publishes the release on main. A pull request whose patch no longer applies fails.

Changing a patch

Edit in a forgejo-runner clone on top of UPSTREAM_VERSION, run git format-patch <tag> -o patches/ and push to main. The release for that version is replaced.