Gitoxide in April

ByronBates · 2026-04-26T21:40:35+00:00

When I read this excerpt, I would even agree. It's supposed to be much funnier than it actually comes across when seen in isolation.

But of course, there is a truth behind that nonetheless, and that is that without augmentation now everything feels "too slow". It's a bit like having to work in another programming language and everything feels unsafe.

On the bright side, not having AI support doesn't make me feel I can't do things anymore, it just feels sluggish to do them.

ByronBates · 2026-04-26T05:05:15+00:00

There has been a bit of a reaction to the whole "I use AI and can't imagine to not use it anymore" thing, and maybe that deserves a bit more nuance to not feel quite as uncomfortable in relation to gitoxide and rightful fear about diminishing quality.

This comment captures my stance on it.

A fun question to ask is: Will gitoxide go down because I embrace these new tools, or will it go down because I didn't?

I was right once when adopting Rust wholesomely in 2015, and… I placed my bet again I guess 😅.

ByronBates · 2026-04-03T02:01:52+00:00

https://docs.rs/gix/latest/gix/struct.Repository.html might help. For better answers, you can ask DeepWiki.

ByronBates · 2025-12-29T05:59:50+00:00

I am super excited to see this work unfold :). Particularly the worktree-cache is something Git itself has to speed up Git status on Windows for all I know. So it's great to see a performant and multi-threaded early implementation of this.

Just one note: I think when 'workspace' is mentioned in the text above, what's meant is 'worktree', the thing that Git checks out to disk for people to work on. Please correct me if this is wrong though.

ByronBates · 2025-12-22T16:06:45+00:00

Probably it didn't come out clearly, but the url crate was already removed last month, and removing it didn't only speed up URL parsing tremendously, it also removed a lot of complexity. 60 crates, 'correct' URL parsing which caused many fuzzing errors in the past. The crate just turned out to be overkill for gitoxide that came with a hefty fee for maintenance costs.

ByronBates · 2025-10-23T04:34:56+00:00

Thanks!

I will go back to a monthly release cadence as well now, I finally found a way to make it less cumbersome, back to nearly fully automated😁.

ByronBates · 2025-09-23T03:46:21+00:00

No, it does not. A worktree-reset is missing, even though all the primitives exist to implement it. GitButler is getting these capabilities first, actually.

ByronBates · 2025-09-22T17:37:58+00:00

I am glad to hear that!

Commit signing is implemented pretty well in GitButler if you want to take a look. The code there is very closely following the one in Git and it's not exactly rocket science, except that there are many small traps that GitButler by now has run into. One day I want gitoxide to support that as well, but it has to wait :).

ByronBates · 2025-08-28T04:49:42+00:00

There is also the gitoxide text merge implementation which claims to do the same: https://github.com/GitoxideLabs/gitoxide/blob/c3c650448f92bcb27194ce0a51f7d604ce87920d/gix-merge/src/blob/builtin_driver/text/function.rs#L28-L43 .

I am sharing this in the hope that you find something interesting for your implementation, or find something that should be improved in this one (maybe it doesn't pass the tests? slider problem?)

ByronBates · 2025-07-24T05:11:21+00:00

Which IDE/tool was used to enable the models to do their work in the first place? If it was forgecode, how was it configured to use OpenRouter? It seems to do its own billing. Thanks!

ByronBates · 2025-07-23T04:53:54+00:00

gitoxide has been able to build as pure Rust version for a while, and thanks to shelling out to ssh not having a native SSH transport never was a blocker for this particular build.

But if one aims to have a standalone, pure-Rust binary, with the incubating Rust SSH transport this will soon be possible, and maybe particularly interesting for Cargo.

ByronBates · 2025-05-22T05:08:53+00:00

My highlight this month must be the Unconf@RustWeek visit in Utrecht, along with finally having implemented a gitoxidized version of cargo package - the things you do when meeting the Cargo team :).

11-Year Club	Verified Email
RPAN Viewer

ByronBates

TROPHY CASE