Tally All #Git Trailers in a Repository
I’ve been using a lot of #Git Trailers in my commit messages recently and as my thinking on which trailer keys to use has evolved, it’s been useful to look back at which ones have been used before.
https://calebhearth.com/m/tally-git-trailers
#Shell #{{ tags.1 }} #{{ tags.2 }}
Thank you for sharing, that's an interesting viewpoint.
I have never felt constrained by #git. I've always felt that the things I wanted to do were possible, even if at times they were difficult to accomplish.
I like the idea of jujutsu as a tool that has learned from the many years of git's existence. I like some of the early things I see, but using it has been a challenge for me.
I feel like my mental model of get is pretty good, and my model of #jujutsu is not really solid.
I just got the first practical usage of using git interactive rebase.
I did edited multiple files and did need to reverse one of them already committed. I used an interactive rebase to edit the commit, unstaged everything, staged the file required and committed them once again.
Restored the file I want to reset and completed the rebase. That was nice.
https://learngitbranching.js.org/ -- anybody tried this #git training website already ?
¡Ja! Mensajes de commit divertidos... Típico de hackatón.
#Git
️ Microsoft Releases o3 and o4-mini Reasoning Models on Azure
Let's see what the PHP gods say about that "bug"
[Anubis] Utiliser la preuve de travail pour bloquer les robots https://www.journalduhacker.net/s/ew7xa9/anubis_utiliser_la_preuve_de_travail_pour https://www.pofilo.fr/post/2025/04/14-mise-en-place-anubis/ #autohébergement #sysadmin #git
Bauplan – Git-for-data pipelines on object storage
Link: https://docs.bauplanlabs.com/en/latest/
Discussion: https://news.ycombinator.com/item?id=43705991
️ GitHub Copilot Features in Visual Studio 17.14 Preview 3
#devdigest #dotnet #net #microsoft #ide #visualstudio #git #github
#LinusTorvalds built #Git in 10 days - and never imagined it would last 20 years
In a mere 10 days, he developed a working version of Git, which was first committed on April 7, 2005. Of course, he'd been thinking about it for a while. BitKeeper conflict had been brewing almost since the start. In a recent GitHub interview, #Torvalds had been facing a question, "How do I do something that works even better than BitKeeper does but doesn't do it the way BitKeeper does it?"
https://www.zdnet.com/article/linus-torvalds-built-git-in-10-days-and-never-imagined-it-would-last-20-years/?utm_source=changelog-news
#Git mini tip:
Acknowledge co-authors with a 'co-authored-by' trailer at the end of your commit message, like:
co-authored-by: Otter Coder <otter@coolmail.example>
GitHub, GitLab, and some other Git hosts will parse such trailers and show co-authors’ avatars alongside your own for that commit.
Many moons ago I made two idiot proofing changes to my #Git setup
1. adding the alias gi=git
2. enabling the `help.autocorrect` config option
Today it finally kicked in when I typed `gi tshow`
Thanks past me who clearly had no faith in the future me.
me: Hi #git, please just take the stuff I changed and put it on the webernet.
Git: Some updates were rejected because you have un-sprongled verterbrae in your sub-spline. Either extrapolate your tips or re-fling your local branch, using git reblog --ff-no-ice. If you want to recapitulate your local flange, then your diversionary remote can't be submitted without stripping the exoplanet, with potential universal anguish.
hint: Disable this message with "git config set advice.flagelate false"
Needed to merge one git repository into another for the umpteenth time. This way retains history and issue links:
https://rossabaker.com/articles/merge-two-git-repositories-with-history/
