Rename .github/ to .forgejo/ for clarity #22

New issue

Closed

opened 2026-07-05 07:46:12 +08:00 by weiwen · 0 comments

weiwen commented

2026-07-05 07:46:12 +08:00

Owner

What to build

Move the workflow configuration from .github/ to .forgejo/ so the directory name reflects that Forgejo Actions — not GitHub — is the runner of record. The Forgejo runner reads .forgejo/workflows natively.

This is a small, mechanical change, but it must be done in isolation: it relocates the entire workflows directory, so it conflicts with any concurrent or in-review change that adds or edits a workflow. It must land after #21 (which introduces .github/workflows/pr-triage.yml) so the rename carries that file too, and no other workflow-touching work may be in flight at the same time.

Tradeoff to confirm before doing this: .github/workflows was originally kept "for compatibility" so the same files would also work on a GitHub mirror. Renaming to .forgejo makes the workflows Forgejo-specific and drops GitHub-mirror Actions execution. Proceed only if the GitHub mirror is not relied on to run Actions (it is described as a mirror only).

Also update every in-repo reference to the old path (docs/agents, .sandcastle prompts, CONTEXT/DESIGN/README, etc.) to the new .forgejo/ location.

Acceptance criteria

.github/workflows/* moved to .forgejo/workflows/* (including ci.yml and the pr-triage.yml added in #21); the .github/ directory is removed if nothing else remains in it.
Forgejo CI still runs on push and pull_request after the move (the runner picks up .forgejo/workflows), verified green on the PR.
All in-repo references to .github/workflows are updated to .forgejo/workflows.
The GitHub-mirror compatibility tradeoff is confirmed acceptable (or explicitly documented as accepted).

Blocked by

#21 (adds a workflow file the rename must carry; #21 is itself after #20). Additionally, this must NOT be worked on concurrently with any issue that adds or edits a workflow.

## What to build Move the workflow configuration from `.github/` to `.forgejo/` so the directory name reflects that Forgejo Actions — not GitHub — is the runner of record. The Forgejo runner reads `.forgejo/workflows` natively. This is a small, mechanical change, but it must be done in **isolation**: it relocates the entire workflows directory, so it conflicts with any concurrent or in-review change that adds or edits a workflow. It must land **after** #21 (which introduces `.github/workflows/pr-triage.yml`) so the rename carries that file too, and no other workflow-touching work may be in flight at the same time. Tradeoff to confirm before doing this: `.github/workflows` was originally kept "for compatibility" so the same files would also work on a GitHub mirror. Renaming to `.forgejo` makes the workflows Forgejo-specific and drops GitHub-mirror Actions execution. Proceed only if the GitHub mirror is not relied on to run Actions (it is described as a mirror only). Also update every in-repo reference to the old path (docs/agents, `.sandcastle` prompts, CONTEXT/DESIGN/README, etc.) to the new `.forgejo/` location. ## Acceptance criteria - [ ] `.github/workflows/*` moved to `.forgejo/workflows/*` (including `ci.yml` and the `pr-triage.yml` added in #21); the `.github/` directory is removed if nothing else remains in it. - [ ] Forgejo CI still runs on push and pull_request after the move (the runner picks up `.forgejo/workflows`), verified green on the PR. - [ ] All in-repo references to `.github/workflows` are updated to `.forgejo/workflows`. - [ ] The GitHub-mirror compatibility tradeoff is confirmed acceptable (or explicitly documented as accepted). ## Blocked by - #21 (adds a workflow file the rename must carry; #21 is itself after #20). Additionally, this must NOT be worked on concurrently with any issue that adds or edits a workflow.

weiwen added the

ready-for-agent

label

2026-07-05 07:46:12 +08:00

weiwen referenced this issue from a commit

2026-07-06 01:25:51 +08:00

chore: rename .github/ to .forgejo/ — closes #22

weiwen closed this issue

2026-07-06 01:25:51 +08:00