Git Credential Manager for Windows VS Gitea

deprecated Git Credential Manager for Windows: This tool was deprecated after the Core one was created, and it is no longer maintained.

It now defaults to its own manager "manager-core". See: https://github.com/microsoft/Git-Credential-Manager-for-Windows#readme

See this issue: https://github.com/go-gitea/gitea/issues/1029

For years, "self-hosting" Gitea wasn't done because it was missing a bunch of useful collaboration features. Now, it looks like that gap has been closed. All of the specific features mentioned in that issue seem to have been fixed, and the big remaining task is figuring out below to actually migrate all the existing data out of GitHub -- which doesn't seem to be super high on the priority list.

We're not, and they're still in the process of discussion. It seems a bit early to fork and witch-hunt [0]:

> So clarification here: you asked me about that, but I haven’t been able to respond to you due to my illnesses and I’m just getting back on my feet now. So it’s not that it hasn’t been well received, it’s that I’ve been physically unable to respond to you.

[0]: https://github.com/go-gitea/gitea/pull/24257#issuecomment-23...

Yeah, I'm actually doing that with Gitea: https://about.gitea.com/

Some people went with the forgejo fork: https://forgejo.org/ though Gitea itself was a fork of Gogs, if I remember correctly: https://gogs.io/

I also ran GitLab in the past: https://about.gitlab.com/ but keeping it updated and giving it enough resources for it to be happy was troublesome.

There's also GitBucket: https://gitbucket.github.io/ and some other platforms, though those tend to be a little bit more niche.

Either way, there's lots of nice options out there, albeit I'd still have to admit that just using GitHub or cloud GitLab version would be easier for most folks. Convenience and all.

Create a system service. Download the file and save it to /etc/systemd/system/ or view the raw file in a browser and replace the URL with the version of Gitea you installed. You can find the list on https://github.com/go-gitea/gitea/blob/release/v1.22/contrib/systemd/gitea.service:

Same [1]. Zoom being outsourced to the implementing platform is one major pain-point. That example from us has grown in size.

We are clearly using the wrong tool for a diagram of this complexity, but the practicality of seeing commit changes in the diff, what property was changed by whom and instantly having the visual feedback in the Pull Request is just way too useful to use a "proper" tool.

[1] https://github.com/go-gitea/gitea/issues/25803

It's a tangent, but I think it's interesting that Gitea started trying to self host in Feb 2017 (https://github.com/go-gitea/gitea/issues/1029) and hasn't got there yet (based on how active the github issues/PR page are).

https://about.gitea.com/ offers me a "free cloud trial" and otherwise sounds very like other web front ends to git. So like github, except they don't trust it themselves.

In contract forgejo has "Self-hosted alternative to GitHub" written in big letters on the landing page. https://codeberg.org/forgejo is indeed self hosted.

Gitea is a versatile tool for creating and managing git-based repositories, streamlining Code Review to enhance code quality for users and businesses. It integrates a CI/CD system, Gitea Actions, compatible with GitHub Actions, allowing users to create workflows in YAML or use existing plugins. Gitea's project management features include issue tasks, labeling, and kanban boards for efficient management of requirements, features, and bugs. These tools integrate with branches, tags, milestones, assignments, time tracking, and dependencies to plan and track development progress. Furthermore, Gitea supports over 20 package management types, such as Cargo, Composer, NPM, and PyPI, catering to a wide range of public or private package management needs. This comprehensive suite of features makes Gitea a powerful platform for managing development projects and packages.