Yeah
-
This post did not contain any content.
I like git(hub) because you can track changes. Not just versions
-
This post did not contain any content.
The bottom picture should be SVN. I miss incremental revision numbers.
-
This post did not contain any content.
-
This post did not contain any content.
-
I like git(hub) because you can track changes. Not just versions
wrote last edited by [email protected]Gitlab, Gogs, Gitea... you can run all those locally.
-
The bottom picture should be SVN. I miss incremental revision numbers.
wrote last edited by [email protected]SVN is still great if there is a need for strict access controls and central control matters a lot. Auditing is also a bit easier with SVN.
It caters more for a linear workflow, though. So modern large teams won't find joy with SVN.
-
This post did not contain any content.
Can't see media posted by sh.itjust.works users.
Location: India
Anyone else facing the same problem?
-
This post did not contain any content.
Naw, text layers in a .xcf is where it's at.
-
Gitlab, Gogs, Gitea... you can run all those locally.
wrote last edited by [email protected]But how often do you need that for your personal projects? I just have a git repo on a server that's accessible by ssh. I only use a web frontend when I have to share with other people and then you might as well use a free third party service.
-
This post did not contain any content.
Reject GitHub. Embrace Codeberg!
-
What did GitHub do?
Owned by Microsoft. Microsoft recently blocked e-mail access to a LibreOffice dev. Speculation is that they'll start blocking projects for competing products next.
(Alternative explanation: Gitlab should be part of IT divestment from US-based services.)
-
SVN is still great if there is a need for strict access controls and central control matters a lot. Auditing is also a bit easier with SVN.
It caters more for a linear workflow, though. So modern large teams won't find joy with SVN.
wrote last edited by [email protected]It caters more for a linear workflow, though. So modern large teams won't find joy with SVN
For what it's worth, I work at a FAANG company and we don't use branches at all. Instead, we use feature flags. Source control history is linear with no merges.
All code changes have to go though code review before they can be committed to the main repo. Pull requests are usually not too large (we aim for ~300 lines max), contain a single commit, aren't long-lived (often merged the same day they're submitted unless they're very controversial), can be stacked to handle dependencies between them ("stacked diffs"), and a whole stack can be landed together. When merged, everything is committed directly to the main branch, which all developers are working off of.
I know that both Google and Meta take this approach, and probably other companies too.
-
Reject GitHub. Embrace Codeberg!
I would love a subscription to Codeberg to be able to store private projects though. Codeberg is nice but you need an alternative for those special projects and it's annoying.
-
The bottom picture should be SVN. I miss incremental revision numbers.
The mixed-revisions bug was fun... Also cannot clean history or make shitty branches everywhere, it was one of my worst experience. Nowadays Jujutsu is my favorite.
-
This post did not contain any content.
You don't need GitHub for Git.
-
The bottom picture should be SVN. I miss incremental revision numbers.
git rev-list HEAD | wc -l -
It caters more for a linear workflow, though. So modern large teams won't find joy with SVN
For what it's worth, I work at a FAANG company and we don't use branches at all. Instead, we use feature flags. Source control history is linear with no merges.
All code changes have to go though code review before they can be committed to the main repo. Pull requests are usually not too large (we aim for ~300 lines max), contain a single commit, aren't long-lived (often merged the same day they're submitted unless they're very controversial), can be stacked to handle dependencies between them ("stacked diffs"), and a whole stack can be landed together. When merged, everything is committed directly to the main branch, which all developers are working off of.
I know that both Google and Meta take this approach, and probably other companies too.
Trunk based dev is GOAT.
-
This post did not contain any content.
Armatures!
Project. New
Project.new.new
