!git
@programming.devhttps://blog.git-init.com/how-does-git-store-files/
In this post, I'll show you how project files and folders are stored, and how they relate to the overarching commit history — all from a conceptual point of view.
https://til.simonwillison.net/git/backdate-git-commits
I fell down a bit of a rabbit hole this morning. In trying to figure out where the idea of celebrating World Wide Web Day on August 1st came from I ran across Tim Berner-Lee's original code for the WorldWideWeb application for NeXT on the W3C's website:
https://git.github.io/rev_news/2024/07/31/edition-113/
https://youtube.com/watch?v=ntM7utSjeVU
Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
https://github.blog/open-source/git/highlights-from-git-2-46/
Git 2.46 is here with new features like pseudo-merge bitmaps, more capable credential helpers, and a new git config command. Check out our coverage on some of the highlights here.
https://github.com/opensourcecorp/vdm
A General-Purpose Versioned-Dependency Manager. Contribute to opensourcecorp/vdm development by creating an account on GitHub.
https://matklad.github.io/2024/07/25/git-worktrees.html
There are a bunch of posts on the internet about using git worktree command. As far as I can tell, most of them are primarily about using worktrees as a replacement of, or a supplement to git branches. Instead of switching branches, you just change directories. This is also how I originally had useed worktrees, but that didn't stick, and I abandoned them. But recently worktrees grew on me, though my new use-case is unlike branching.
I think it's generally agreed upon that large files that change often do not belong while small files that never change are fine. But there's still a lot of middle ground where the answer is not so clear to me.
So what's your stance on this? Where do you draw the line?
https://schpet.com/note/git-commit-messages-are-optional
https://pr.pico.sh/