ci: run CI on Forgejo Actions with lean .forgejo workflows #6

Open

ggrace wants to merge 5 commits from ci/forgejo-workflows into develop

pull from: ci/forgejo-workflows

merge into: ggrace:develop

ggrace:master

ggrace:dependabot/npm_and_yarn/langchain/mongodb-1.3.1

ggrace:dependabot/npm_and_yarn/packages/cli/handlebars-4.7.10

ggrace:develop

ggrace:dependabot/npm_and_yarn/vm2-3.12.2

ggrace:dependabot/npm_and_yarn/simple-git-4.0.1

ggrace:fix/editor-vars-workflow-project

Conversation 0 Commits 5 Files changed 3 +129

ggrace commented 2026-10-10 07:34:12 -04:00

Owner

Copy link

Summary

The upstream .github/workflows fail on the self-hosted Forgejo runners (workflow_call reusable workflows fire on every event, blacksmith-*/windows-latest runners, upstream-only secrets). This adds lean workflows under .forgejo/workflows/ that Forgejo uses instead; .github/ is untouched for upstream merges.

Jobs (all ubuntu-latest): build + typecheck, lint (pnpm lint:ci), backend unit, nodes unit, frontend unit.

Verification

This PR is its own test: its CI run is the first run of the new workflows.

🤖 Generated with Claude Code

## Summary The upstream `.github/workflows` fail on the self-hosted Forgejo runners (`workflow_call` reusable workflows fire on every event, `blacksmith-*`/`windows-latest` runners, upstream-only secrets). This adds lean workflows under `.forgejo/workflows/` that Forgejo uses instead; `.github/` is untouched for upstream merges. Jobs (all `ubuntu-latest`): build + typecheck, lint (`pnpm lint:ci`), backend unit, nodes unit, frontend unit. ## Verification This PR is its own test: its CI run is the first run of the new workflows. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ggrace added 1 commit 2026-10-10 07:34:12 -04:00

ci: run CI on Forgejo Actions with lean .forgejo workflows ... e90726f2d6

The upstream .github workflows rely on workflow_call, blacksmith runners and
upstream-only secrets, so they fail on the self-hosted Forgejo runners.
Add build/typecheck, lint and unit-test workflows under .forgejo/workflows,
which Forgejo uses in place of .github/workflows.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

ggrace added 1 commit 2026-10-10 07:43:41 -04:00

ci: set CI=true so pnpm install skips the lefthook prepare step ... d1172bc690

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

ggrace added 1 commit 2026-10-20 22:17:03 -04:00

ci: set CI on the composite install step ... b0bcf02552

The Forgejo runner doesn't carry workflow-level env into composite action
steps, so `pnpm install` ran the root `prepare` script, whose lefthook
install exits non-zero inside the job container. Reproduced in the
runner's own image: install fails with a bare ELIFECYCLE without CI and
passes with it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

ggrace added 1 commit 2026-10-20 22:29:44 -04:00

ci: log pnpm install at info level instead of setting CI on the step ... 7a549af49e

Setting CI on the install step (previous commit) didn't change the
failure: the job still dies in a dependency install script, and at the
repo's default warn level pnpm reports only a bare ELIFECYCLE. Log the
install at info so the failing script's output reaches the job log.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

ggrace added 1 commit 2026-10-20 22:34:06 -04:00

ci: clear GITHUB_TOKEN for pnpm install so ripgrep's download works ... 5f457daa98

The runner exports GITHUB_TOKEN as its Forgejo job token. @vscode/ripgrep's
postinstall forwards any GITHUB_TOKEN to api.github.com, which answers 401,
so every install failed after its retries. With the variable empty the
request is anonymous and succeeds (verified against the real script with a
fresh download cache: bogus token -> 401/exit 1, empty -> exit 0).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Some checks failed

Hide all checks

CI / Backend unit tests (pull_request) Has been cancelled

Details

CI / Nodes unit tests (pull_request) Has been cancelled

Details

CI / Frontend unit tests (pull_request) Has been cancelled

Details

CI / Build and typecheck (pull_request) Failing after 11m45s

Details

CI / Lint (pull_request) Has been cancelled

Details

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin ci/forgejo-workflows:ci/forgejo-workflows

git switch ci/forgejo-workflows

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch develop

git merge --no-ff ci/forgejo-workflows

git switch ci/forgejo-workflows

git rebase develop

git switch develop

git merge --ff-only ci/forgejo-workflows

git switch ci/forgejo-workflows

git rebase develop

git switch develop

git merge --no-ff ci/forgejo-workflows

git switch develop

git merge --squash ci/forgejo-workflows

git switch develop

git merge --ff-only ci/forgejo-workflows

git switch develop

git merge ci/forgejo-workflows

git push origin develop

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ggrace/n8n!6

No description provided.