Skip to content

chore: rename module to github.com/go-semantic-release/provider-gitea - #9

Merged
guisea merged 1 commit into
mainfrom
chore/module-rename
Sep 8, 2026
Merged

guisea merged 1 commit into
mainfrom
chore/module-rename

Conversation

@guisea

@guisea guisea commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Closes #6.

When the repo moved to the go-semantic-release org, the module path and several references were left pointing at the old personal locations.

File Change
go.mod module github.com/cybercinch/go-semantic-release-provider-gitea → github.com/go-semantic-release/provider-gitea
_cmd/provider-gitea/main.go import path updated
.goreleaser.yaml ldflags -X ...pkg/provider.PVERSION target updated
README.md CI badge → go-semantic-release/provider-gitea; slug example updated

pkg/provider/*.go are all in-package, so no import changes there.

Left as-is (separate personal infra, noted in #6): the badges.cybercinch.nz coverage-badge host and cybercinch/dynamic-badges-action.

go build ./... ./_cmd/provider-gitea/, go test ./..., go vet, and golangci-lint all pass.

The module path and README badge/slug references still pointed at the
pre-transfer personal locations (github.com/cybercinch/..., guisea/...).
Update go.mod, the _cmd import, the goreleaser ldflags -X target, and the
README CI badge and slug example to the org path.

The cybercinch.nz coverage-badge host and dynamic-badges-action remain
(separate personal infra, tracked in #6).

Closes #6
@guisea
guisea merged commit df3f352 into main Sep 8, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update module path after move to go-semantic-release org

1 participant