Git

Headlines:

• Faster packing with name-hash v2
• Backfill historical blobs in partial clones

Followed by some more technical notes.

Hi there, we are a small tram of social researchers working on writing a collective report together. The report has several chapters. Our plan is to use git to store changes and easily traceback to different versions as well as allowing everyone to experiment with new ideas.

I am trying to decide a branching strategy, and so far I guess something like feature branching could do. We could have a branch for each chapter..? And maybe, when a chapter is kind ready, we could merge into main..?

We will have members working potentially on different parts of the report in different moments.

Advice is needed. Thank you!

I was trying to learn git and after searching a bit, I finally found some good open-source tutorials. Specifically, I followed those two tutorials, in this order:

1. https://ohmygit.org/ (a computer application)
2. https://learngitbranching.js.org/ (a website)

The second seems to cover a bit more advanced topics (it teaches more thoroughly about remote repositories)

Also after an alternativeto search and a post here, I found three more open-source resources:

1. https://www.gitmastery.me/ (a modern website)
2. https://github.com/vishal2376/git-coach (an android application covering the very very basics)
3. https://github.com/jlord/git-it-electron (An old computer application)

PS. Prior to these I had a basic git course, which I think wasn't enough, but probably helped me either way and after this I had checked some git resources, which gave more of a rounded knowledge about git and I think are worth metnioning:

1. https://jdsalaro.com/tutorial/git/index.html (this person is here on lemmy too)
2. https://tom.preston-werner.com/2009/05/19/the-git-parable.html
3. https://missing.csail.mit.edu/
4. https://docs.codeberg.org/git/clone-commit-via-cli/
5. https://github.com/SimonSchubert/LinuxCommandLibrary

Lastly, there's the pro git book as well for anyone who wants to go even deeper: https://git-scm.com/book/en/v2

Thank you for git - a lovely version control system https://git-scm.com/

#ilovefsday #ilovefs @git @fsfe @torvalds

Hey! I've just released todo-md v1 🚀. Keep your tasks organized with todo-md!

The pre-commit hook automatically maintains a TODO.md file by scanning your staged files for TODO: comments. You do not need complicated task trackers bloated with features anymore:) Let your code speak for itself!

Get it now: https://codeberg.org/lig/todo-md

#TODOmd #DevTools #PreCommit #Automation #OpenSource #Git #Todo​

This is an article in which I explore the details and thinking that goes into how you should create git commits, and why. I like to think of it as the article I wish existed when I was just starting out over 20 years ago.

I wanted to cover all the things that you should think about at a high level. That way it at least could work as an entry point to deeper exploration of the particular areas if the reader isn’t completely sold or they want to just gain a deeper understanding. While at the same time trying to provide enough details to show why and how these choices are valuable. This is always a tricky balance.

Anyways, I would love any feedback on thoughts on how this could be improved.

Thanks