this post was submitted on 13 Jul 2024
156 points (90.6% liked)

Open Source

30924 readers
143 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 48 points 3 months ago (14 children)

It's called git. It's been distributed from day 1. GitHub was an attempt to centralize it.

[–] [email protected] 40 points 3 months ago (13 children)

Yeah... does git have issue tracking? actions? C'mon: it's not like github & co. are just git.

[–] [email protected] 7 points 3 months ago (8 children)

Again, like OP said, those are typically distinct functionality: issue tracking, source control, deployment etc. GitHub bringing everything into one platform is atypical and obviously done for the goal of centralization. The more stuff you add to a platform the harder it makes it to leave or replicate.

But no, technically speaking you don't need to have all of it in one place. There's no reason for which you must manage everything together.

I don't even understand why people like GitHub so much, its source management sucks. The fact it still doesn't have a decent history visualization to this day is mind-boggling.

Look for ways to do things separately and you will find much better tools. GitHub's "one size fits all" approach is terrible and only holds because people are too lazy to look for any alternative.

[–] [email protected] 3 points 3 months ago (2 children)

What combination would you recommend to replace most common GitHub functionality?

[–] [email protected] 1 points 3 months ago

Forgejo should work

[–] [email protected] 2 points 3 months ago

It depends a lot on the setup you have, how many people, release flow etc. Issue tracking depends on the kind of software you do and whether you want a programmer-only flow or a full support flow.

Deploy pipelines will usually depend on the infrastructure, cloud solutions usually can integrate with several and there's also common solutions and even FOSS ones, like Terraform vs OpenTofu.

Git frontends are a very mixed bag, generally speaking their main purpose is to hide Git as much as possible and allow programmers to contribute changes upstream without knowing much beyond the nebulous "PR" concept. Basically they're mostly useless other than enabling people to remain dumb. A good Git tutorial and a good history visualization tool (git happens to include one called gitk out of the box) will do so much more to teach people Git, and there's really no substitute for communication – using annotations to discuss pros and cons for a PR is badly inadequate.

load more comments (5 replies)
load more comments (9 replies)
load more comments (9 replies)