go-git VS git-compose

I interpret "aims to be fully compatible" as meaning the operations it implements are intended to be compatible with how Git implements those operations. I do not interpret this statement as saying they implement all features of Git.

They offer a document which directly shows what is and isn't supported, and it specifically notes quite a few things that aren't supported yet: https://github.com/go-git/go-git/blob/master/COMPATIBILITY.m...

The godoc also says right upfront it "nowadays covers the majority of the plumbing read operations and some of the main write operations, but lacks the main porcelain operations such as merges." - https://pkg.go.dev/github.com/go-git/go-git/v5#pkg-overview

> I'm saying it's not a reasonable choice over just using git directly, and is unlikely to ever be.

OK, that's apparently true for your use-case. But again, what go-git implements is directly useful to a number of very popular projects, as well as literally two thousand less popular ones.

I find the exported functionality to be high quality, at least for my own use-case. I'm not commenting on the code quality. If I need a shed for bikes, and someone is giving out free but ugly bikesheds, I'm thankful. I don't complain about the color of the bikeshed.

The go frameworks has some particular limitations at the moment (merge, rebase https://github.com/go-git/go-git/blob/master/COMPATIBILITY.md) but overall great framework.Used for some go tools..

You can monitor the sha of your config repos main branch with this I expect. https://github.com/go-git/go-git

I'm remaking a package named owl. One of the features of this package is the ability to clone remote repositories. The first time I affront this problem, I solved it using go.Cmd and git command. Is there a way to achieve something similar without importing or using a dependency like go-git. Something like download files via http, ssh or something similar.

I think there are already some Git SDKs out there. For example https://github.com/go-git/go-git

I see that you’re using go-git, which has a problem with worktree.Status being unusably slow—and in a prompt you’ll most certainly need to use it. I know because I tried writing my prompt using go-git, and had it hang on a work repo for a good minute. Eventually bit the bullet and switched to git2go (libgit2 bindings; uses cgo).

Sure, try to fork one of the repos, make changes for any of improvements above and let's see if you can make MR back. You can also try to create issue in one of the projects if you want to discuss some specific problem before making MR (not sure if issues are publicly available though, if not - just write me here, I'll see what I can do). You could for example start with explaining details on push command. That's supposed to change output of gico doc, which is also used to produce published documentation I linked above, as well as man of the debian package (during `promote` job run, which have a restricted access though). Depending on how it works (whether MR from fork would be ok and access to issues), it would help me with the content of Contribution guide.