Programming

426 readers

5 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Git without a forge (www.chiark.greenend.org.uk)

submitted 3 days ago by Hazematman@lemmy.ca to c/programming@programming.dev

10 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ericjmorey@programming.dev 3 points 3 days ago* (last edited 3 days ago)

Introduction

I’ve written quite a lot of free software in my life. Most of it was from scratch: projects I started myself. So I get to choose where to host them – or rather, I have to choose where to host them.

These days, all my projects are held in Git. And mostly, I put them in ‘bare’ git repositories on my personal website.

I don’t use any git ‘forge’ system layered on top of Git, like Gitlab or Github, which automatically makes a bug tracking database for each project, and provides a convenient button for a user to open a merge request / pull request. I just use plain Git. People can ‘git clone’ my code, and there’s a web-based browsing interface (the basic gitweb) for looking around without having to clone it at all. But that’s all the automated facilities you get.

Occasionally this confuses people, so I thought I should write something about it.

Discussion with the author @ https://hachyderm.io/@simontatham/114111520633445984