Change module path to sneak.berlin/go/neoirc #99
Reference in New Issue
Block a user
Delete Branch "change-module-path-to-sneak-berlin"
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?
Changes the Go module path from
git.eeqj.de/sneak/neoirctosneak.berlin/go/neoirc.All occurrences updated:
go.modmodule directive.gofiles (107 import statements)$idURIs across 30.jsonfiles inschema/No functional changes — this is a pure rename of the module path.
docker build .passes clean (formatting, linting, all tests, binary build).closes #98
Review: PR #99 — Change module path to sneak.berlin/go/neoirc
Policy Divergences
No policy violations found.
sneak.berlin/go/<name>as the Go module root — the new pathsneak.berlin/go/neoircis compliant.@sha256:— verified, no changes to Dockerfile..golangci.yml, CI config, or test assertions. No cheating detected.goimportsconvention (stdlib → third-party → internal, alphabetized within groups).Requirements Checklist (issue #98)
git.eeqj.de/sneak/chat(old repo name) /git.eeqj.de/sneak/neoircreferences tosneak.berlin/go/neoircgo.modmodule directive updated.gofiles, 107 import statements)$idURIs updated (30.jsonfiles inschema/)git.eeqj.de/sneak/neoircorgit.eeqj.de/sneak/chat) in any.go,.mod,.jsonfileTest Coverage
No new exported types or functions introduced — this is a pure module path rename. Not applicable.
README Consistency
README.md does not reference the Go module path directly. Remaining
git.eeqj.dereferences in README.md and REPO_POLICIES.md are links to other repositories (prompts, gohttpserver) on the Gitea instance — not this module's import path. No inconsistency.Build Result
docker build .— PASS (formatting, linting, all tests, binary build all clean). Verified both before and after rebase ontomain.Verdict: PASS
Pure mechanical rename of the module path from
git.eeqj.de/sneak/neoirctosneak.berlin/go/neoirc. Every occurrence updated across 65 files. No functional changes, no policy violations, no cheating, build green.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.