CI does not run here: 10 workflows are in .github/, this instance reads .forgejo/ #1

New issue

Open

opened 2026-09-30 17:09:52 +00:00 by forge-ci · 0 comments

forge-ci commented

2026-09-30 17:09:52 +00:00

Member

This repository was extracted from rituals-chat on 2026-09-30 and carries .github/workflows/ with no .forgejo/. On this Forgejo instance those files are inert, so nothing currently runs on push or PR.

These workflows are not dead weight

They ran on GitHub, and their failures reached the forge as wishes:

[toilville/automoto] Run failed: Lint - main
[toilville/automoto] Run failed: Tests - main
[toilville/automoto] Run failed: Security Scan
[toilville/automoto] Run failed: Deploy to Azure

So this is a migration decision, not a mechanical port.

Present in .github/workflows/

codeql.yml, deploy.yml, emu-support-triage.yml, first-interaction.yml, lint.yml, pr-labeler.yml, release-evidence-check.yml, release-gates.yml, security.yml

What needs deciding

Which lanes still apply. deploy.yml targets Azure and codeql.yml is a GitHub-hosted service — neither has a straight Forgejo equivalent. Lint, tests and release-gates do.
Runner labels. Commit d123b80 ("align automoto workflows with self-hosted runners") already moved these off GitHub-hosted runners once. Any port must use the :host label suffix, or jobs silently run inside a Linux Docker container instead of on the host.
Whether .github/ stays. Leaving it is misleading — a green-looking config that cannot fire. Either port and delete, or keep it and say in the README that CI lives elsewhere.

Until this is resolved, treat every merge here as untested.

This repository was extracted from `rituals-chat` on 2026-09-30 and carries `.github/workflows/` with no `.forgejo/`. On this Forgejo instance those files are inert, so **nothing currently runs on push or PR**. ## These workflows are not dead weight They ran on GitHub, and their failures reached the forge as wishes: - `[toilville/automoto] Run failed: Lint - main` - `[toilville/automoto] Run failed: Tests - main` - `[toilville/automoto] Run failed: Security Scan` - `[toilville/automoto] Run failed: Deploy to Azure` So this is a migration decision, not a mechanical port. ## Present in .github/workflows/ `codeql.yml`, `deploy.yml`, `emu-support-triage.yml`, `first-interaction.yml`, `lint.yml`, `pr-labeler.yml`, `release-evidence-check.yml`, `release-gates.yml`, `security.yml` ## What needs deciding 1. **Which lanes still apply.** `deploy.yml` targets Azure and `codeql.yml` is a GitHub-hosted service — neither has a straight Forgejo equivalent. Lint, tests and release-gates do. 2. **Runner labels.** Commit `d123b80` ("align automoto workflows with self-hosted runners") already moved these off GitHub-hosted runners once. Any port must use the `:host` label suffix, or jobs silently run inside a Linux Docker container instead of on the host. 3. **Whether `.github/` stays.** Leaving it is misleading — a green-looking config that cannot fire. Either port and delete, or keep it and say in the README that CI lives elsewhere. Until this is resolved, treat every merge here as untested.