2026-07-16 17:27:59
The #git history command deserves more attention
https://lalitm.com/post/git-history/
The #git history command deserves more attention
https://lalitm.com/post/git-history/
Given these days you can't even expect #Gentoo contributors to be respectable, I'm working on adding a git hook that rejects commits with #LLM attribution. Could you help me find all the common patterns used to mark LLM-assisted #git commits?
So far I'm checking for author and Co-authored-by using the following e-mail patterns:
• copilot@github.com
• *@anthropic.com
• claude@users.noreply.github.com
• * claude[bot]@users.noreply.github.com
• *@openai.com
• * chatgpt-codex-connector[bot]@users.noreply.github.com
• *@cursor.com
• *@x.ai
• *@google.com
I think some people came up with some other tags to mark LLM commits but can't find that right now.
EDIT: added Assisted-by.
#NoAI #NoLLM #AI
:git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully …
Is there an option hidden somewhere in git log / ref-log / mailmap which would support colorizing output lines differently depending on whether a author/committer matches some pattern (eg Mine vs Another Maintainer vs Unknown Contributor)?
I know I could post-process the output of git log or use other plumbing tools, but I'd rather not if something is built-in.
#git #askfedi #devlog
For a long time, I diligently put my course materials into #git, but I found that it has little, if any, benefits for my use case, most notably, working alone.
But I’m now in the lucky position that others will teach my courses for the next academic year (#sabbatical, yay!)—now it does make sense to use version control!
⇢
For a long time, I diligently put my course materials into #git, but I found that it has little, if any, benefits for my use case, most notably, working alone.
But I’m now in the lucky position that others will teach my courses for the next academic year (#sabbatical, yay!)—now it does make sense to use version control!
⇢
For a long time, I diligently put my course materials into #git, but I found that it has little, if any, benefits for my use case, most notably, working alone.
But I’m now in the lucky position that others will teach my courses for the next academic year (#sabbatical, yay!)—now it does make sense to use version control!
⇢
#TIL that #git has an `--end-of-options` option because they used `--` for something else in `git checkout`. 🤦
https://nesbitt.io/2026/07/21/end-of-options.html
(thanks to @… for the link)
We had an intermittent storage issue. This problem has now been resolved.
#opencommit #git #opensource
Zero days since I messed up rebase by using `#git commit --amend` and missing that I was suppose to just `git commit` because it stopped on a merge conflict rather than my "edit".
{piggyback} makes it easier to attach large files (e.g. input data) to code in github repos: #rstats
No, you cannot embed ANSI escape sequences in the mailmap names. That would be horrifying.
(Does this nerd-snipe @… ?)
#git
🔍 #Hunk is a review-first terminal diff viewer for agent-authored changesets #opensource #git #cli