A powerful TUI git server which can be hosted over SSH.

Simple to configure but also very opinionated and deeply embedded in the 'charmbracelet' suite of software (using glow for md display, etc.).

If you need a quick git server, amazing. If you need a lot of deep customization, less so.

We have tea for gitea projects, gh for github and glab for gitlab as easy-to-work-with local commandline interfaces.

This one is simply specifically for forgejo instead and seeks to support a lot of the forgejo-only feature (AGit workflow, federation) that the others won't.

A very nice GUI client for git. Nice design and pretty functional layout - somewhat reminiscent of GitKraken

TUI for Jujutsu/jj, similar to lazygit for git.

'Automatically' generate nice changelogs. Still requires manual intervention to decide what is interesting user-facing changes for the changelog and what is not when finishing features/fixes.

But the idea behind it is to run during CI and take all those changes and package them up into a nicely formatted SemVer changelog so that at that moment everything happens automated.

Also nice to combine with a release automation, e.g. goreleaser, which can then take just the new changes to add to each release.

Gitmoji is an emoji guide for your commit messages. Aims to be a standarization cheatsheet for using emojis on GitHub's commit messages.

Provides a set of kubernetes extensions which allow git repositories to be applied (synced) into a cluster and reconciled in the typical declarative model. It thus seeks to allow GitOps flows to automatically be applied.

I.e. you merge something in git and it applies it to your k8s cluster.

Self-hosted lightweight PaaS solution to deploy and manage your applications on any VPS [Your own self-hosted Heroku, Vercel] - swiftwave-org/swiftwave

Deploy your containers easily and quickly. Smaller footprint than coolify

Host your own containers with a slick cli interface.

An impressive git forge frontend, settling somewhere between GitLab and Gitea/Forgejo.

Provides an impressively robust DevOps pipeline (code reviewing, CICD, commenting, email-to-ticket, semantic code search and more already included out of the box).
Thus probably a bit heavier when deployed compared to Gitea/Forgejo (though they are exceedingly light on resources) but still way lighter than a full GitLab deployment.

Have seen very few instances in the wild so I do not know how well it holds up in the end.

A cli wrapper combining git and dvs. Instead of doing first dvc commit then git commit then individual pushes you can just do it with one fds commit.

Similarly with fds status which is probably the most used command - get a quick at-a-glance overview of current project status for both data and code.

By being built as a wrapper it of course still allows delving into the individual programs for more advanced operations. Pretty clever, actually!

Update multiple repositories in with one command.

Similar to git-xargs but seems to work for repositories not hosted on Github. Takes any kind of script and applies it to all repositories you pass in. Very nice! Only the name is a bit worse.

Very interesting, the name basically gives the game away.
You give the tool a list of git(hub) repositories and a command (or more advanced script files) and it runs it against them.

You could for example create a file in each one. Or change some variable. Or grep and sed something from one thing to another thing. Or or or.

Honestly not seeing myself using it that often - but the fact it exists is fascinating to me, and the naming is just genius. Though I am a little sad that it seems to only work for Github projects.

A walkthrough of the most used functions and setup for git annex. In-depth explanations of the how but not the why - use whenever you already know a use-case for git annex.

An in-depth write up of what git annex is, how to use it and (importantly) why. Explains backup and file location scenarios.

Open-source version control system for Data Science and Machine Learning projects. Git-like experience to organize your data, models, and experiments.

A way to track data - even if it is in different locations - alongside code, mimicking its version control. Seems a little complicated but really useful, especially with additional features like data pipelines that are contained

One step to check out github pull (and I believe gitlab merge) requests locally:

git fetch origin pull/1234/head:pr-1234

• origin is the remote origin you want to pull from, the one pull requests have been done against (e.g. your own repository if others have created pull requests there)
• pull/1234/head should have the number of the pull request you want
• :pr-1234 is the local branch you will create - it has to be a new branch

Commandline tool for gitea, can show issues, pull requests, and more.

Very helpful steps for first locating an old file in your git history you only roughly remember the name of, then browsing through its history, then finding exactly what you want.

"🤖 A decorated enhanced elegant, feature rich and modern private git ui repository viewer"

Looks a little like a debloated gitea (which is already quite a debloated gitlab). Nice to look at, only made for browsing so no interaction, pull request, users, issues, merge requests, wiki, etc.

But a nice branch network graph and commit logs, README preview and repository browser.