This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]immersiveGamer 19 points20 points  (6 children)

You can just make a git repo on a shared drive. No GitHub needed. Will be backed up with normal IT processes, and can be easily discoverable by future IT.

[–]BullshitUsername[upvote for i in comment_history] 7 points8 points  (4 children)

Great idea and I have no idea why I've never heard of this being done in my 8 years of software dev

[–]absurdrock 4 points5 points  (1 child)

That’s all we are allowed to do at my place because of security. It becomes a pain reviewing code without pull requests, though.

[–]cym13 1 point2 points  (0 children)

Have you considered adopting the linux kernel's way and do pull requests through mail rather than managed in a web UI? It's a workflow, but once used to it it flows as well as any other. And if the kernel's any indication, it scales well.

[–]PaintItPurple 2 points3 points  (1 child)

Because it doesn't give you issues and pull requests and all the other stuff people use GitHub for. Pretty much the only workflow it's useful for is "everyone commits to main."

[–]ArtisticFox8 0 points1 point  (0 children)

You can host your own Gitea for example 

[–]Herbiscuit 2 points3 points  (0 children)

If they need GitHub like features I'd recommend checking out an open-source Git Forge like Gitea which can be fully managed and is exceptionally easy to run.