GitView v0.1.9
GitView v0.1.9
Bridge-only release. The bridge goes to 0.1.9; the app is unchanged and stays at 0.1.8 — the
gitview-0.1.8.apk from the previous release is still current, and there is no new APK here.
The diff view no longer refreshes on a loop
On a repository with submodules, simply viewing a diff could make it re-render about once a second,
which made reading or scrolling one almost impossible.
Serving a diff makes git take a lock file inside each submodule. The bridge treated that lock as a real
change and told the app, the app re-fetched the diff, and that took the lock again. The trigger was the
request itself, so it only appeared while you had a diff open — and it looked like a machine-specific
problem when it was really a matter of how recently a repo's submodules had been refreshed.
Transient git internals are now filtered at every level of a repository, not just the top, so this cannot
feed itself. Real changes are unaffected: editing a file inside a submodule still updates the view, as
does any genuine git activity — a fetch, a branch switch, a commit.
A submodule's own .gitignore is now honoured
Related and previously impossible: ignore rules inside a submodule had no effect, because the check the
bridge used refuses any path belonging to a submodule and quietly gave up on the whole batch when it hit
one. Ignore filtering is now done per repository, so build output under a submodule — an ESP-IDF build/
directory, for instance — no longer reaches the app at all.
This also means the gitignore filtering added in 0.1.8 genuinely applies to submodule repositories for the
first time; on those it had been silently inactive.
Upgrading
Nothing to do beyond installing the .deb. No re-pair, no configuration change, and no new APK — your
paired devices and tokens are untouched. The service restarts itself, so the app reconnects within a few
seconds.
Install
sudo dpkg -i gitview-bridge_0.1.9_all.deb
Debian/Ubuntu, Architecture: all; requires Node.js ≥ 20 on the host.
Verify
sha256sum -c SHA256SUMS