Tootfinder

#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)

The #git history command deserves more attention
https://lalitm.com/post/git-history/

Periodic reminder that I maintain a list of git resources - a collection of extra commands, links to useful utilities, links to blog posts, etc.
#git #sre #devops

🤖 some #Git users may be interested into this bash script that analyses your git diff and creates meaningful commit messages using an #Ollama #LLM (local / cloud).

🤖 A bash script that analyses your git diff and creates meaningful commit messages using an Ollama LLM (local / cloud).
🤖 A bash script that analyses your git diff and creates meaningful commit messages using an Ollama LLM (local / cloud). - llm-commit.sh

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

#Git Is Not Fine
https://www.billjings.com/posts/title/git-is-not-fine/

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!
⇢

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

GitHub - ropensci/piggyback: :package: for using large(r) data files on GitHub
:package: for using large(r) data files on GitHub. Contribute to ropensci/piggyback development by creating an account on GitHub.

: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 …

We had an intermittent storage issue. This problem has now been resolved.
#opencommit #git #opensource

No, you cannot embed ANSI escape sequences in the mailmap names. That would be horrifying.
(Does this nerd-snipe @… ?)
#git

Cool! These should all be green; somehow, the least expected OS to work passed the test, while the top and medium expected OS didn't. Fun!
#git #linux #windows

« J'ai découvert Beads, Dolt et DoltgreSQL »
#Git #PostgreSQL

Wow, :gitannex: #gitAnnex not generally forcing existence of a synced/main branch anymore? Sounds like an amazing change that will reduce confusion and the branch juggling. 👍
http://

Been coding a lot lately. If anyone is looking for a selfhosted git repository manager, Forgejo is absolutely great to work with! #selfhosted #programming #git

« J'ai découvert Beads, Dolt et DoltgreSQL »
#Git #PostgreSQL

My :forgejo: #forgejo now takes >20s to load the activity page 🤡
This is on cold starts, subsequent refreshes are fast. I think I have reached the limit storing forgejo's data on a WD4TB USB disk, using an sqlite database and having a *ridiculous* amount of commits due to :gitannex: #gitAnnex

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

Would be really great if
> nix run codeberg:user/repo
was possible. It works for #GitLab and #GitHub already. #Codeberg should also work. Instead, one needs to write this unergonomic thing:

feat: flake input type "`codeberg`" · Issue #14064 · NixOS/nix
Problem Flakes targeting a remote hosted on codeberg need to use the git type It is not as efficient as a dedicated "codeberg" flake input type, and cumbersome to write Proposed solution Feature a ...

> Users of #GitHub's command-line interface (#CLI) who value #privacy, beware. The #Microsoft-owned code-hosting platform has quietly begun collecting pseudonymous client-side #telemetry from CLI users and enabled it by default.
Wed 22 Apr 2026, Brandon Vigliarolo, The Register: #Datenschutz #TeamDatenschutz #DataProtection #DiDay