CodeTrunk the new GitBuild

gitbuild.dev is getting a new name. The service you use today will soon be called CodeTrunk, at codetrunk.eu. Everything else stays exactly the same. This post is the longer version of why.

Why the name has to change

When I launched, I named the service "gitbuild": git, plus the building you do with it. The problem was baked into that choice. The Git project's trademark policy does not allow "Git" as part of a product name, and the project no longer grants exceptions. I asked Software Freedom Conservancy, stewards of the Git trademark, for one anyway. The answer was no.

Their name, their rules, and honestly a defensible policy: a name like mine implies an affiliation that does not exist. I committed to retiring the name within weeks, and that deadline is now close. So: new name.

Why CodeTrunk

A trunk is where you store things, and trunk-based development is how many of us like to work. CodeTrunk carries both meanings. It is short, distinctive enough to trademark properly, and works in Dutch, German, French, and English without tripping anyone. The .eu domain fits the positioning: EU hosting, EU company, EU data.

What changes for you

The name and the domain. That is the complete list.

• Your account, repositories, issues, pull requests, organizations, and subscription carry over untouched. Prices don't change.
• Same company (StennMedia, Netherlands), same EU infrastructure, same Forgejo under the hood, same person answering support.
• Nothing to configure, migrate, or re-authenticate.

And to be precise about "nothing breaks":

• gitbuild.dev redirects to codetrunk.eu page for page, bookmarks included, for at least 12 months.
• Git remotes on git.gitbuild.dev keep working indefinitely. Current clones push and pull untouched; new repositories will show repos.codetrunk.eu as their clone URL, and both forms work.
• Login and connected OAuth apps keep working across the switch.

What happens next

Customers receive a service announcement mail with the short version, and a banner on the dashboard as the switch approaches. Once it is done, I send a short confirmation and post an update here.

If you want the engineering side of the move (dual-serving two domains, a git forge that answers to two names, an SEO migration that keeps every ranking), that is exactly the kind of deep-dive the newsletter gets first: join the newsletter.

Questions, worries, or feelings about the old name: write to info@stennmedia.nl, or reply to the announcement mail. It reaches me.