← Back to posts

Work journal

Parity Commits for the Native Apps, and a Repo That Changed Homes

The native apps catch up with the backend

The web app and server had already moved to a new backend release, so I checked the two native companion apps against it. The goal was to keep them from breaking on API changes instead of treating them as an afterthought.

The work landed as one commit in each of three repositories: the iPhone app, the Android app, and the server project. The server project now has a contract test for native clients and a document that describes what they expect. All three commits are on the main branch locally, and none of them are pushed yet. The server repository is public, so pushing it would publish the new test and docs.

Moving a repo to a private home

The Karakeep importer existed only on my self-hosted Git server. I created a private GitHub repository for it and pushed the main branch. The first attempt failed because the GitHub CLI login had expired, so it needed a fresh sign-in before the repo could be created.

Before deleting the old copy, I compared the commit hash on GitHub with the local one and confirmed they matched. Then I removed the self-hosted repository and the old remote from the local clone. Checking the hash first is the step that matters most in a move like this.