Rename the project to fejkdata and record the fork source #1
Reference in New Issue
Block a user
Delete Branch "rename-to-fejkdata"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Renames the package, module path, exported type, CLI, test helpers and error prefixes from fakes to fejkdata, and notes the upstream fork source under the README heading. The English word "fake" (the Fake method, "fake data" prose) is deliberately untouched.
The module path moves to gitea.larvit.se/larvit/fejkdata, where the fork actually lives — the Gitea instance serves the go-import meta tag for it and the path resolves through the Go proxy.
Second commit fixes the merge gate, which was already red on main before the rename: the workflow was inherited from GitHub, where 'docker compose run --rm ci' bind-mounts the source. Under Gitea's act_runner the job is itself a container, so '.' is not a host path and /app came up empty ('directory prefix . does not contain main module'). CI now runs 'docker build', which streams the context to the daemon. The Dockerfile was already advertised as the CI-equivalent gate but skipped the format check, so that check moved into it and the redundant compose 'ci' service is gone — one definition of the gate.