Tootfinder

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

GitFarm: #Git as a Service for Large-Scale #Monorepos
https://www.uber.com/us/en/blog/gitfarm-as-a…

Why is .config/ in git repositories not a thing? As an XDG_CONFIG equivalent to move .vscode, .zed, .forgejo away from the repository root, that would be pretty nice.
#git #forgejo #gitea

🌿 Mirrors Git diff-style commands: hunk diff, hunk show HEAD~1, file-to-file compare and patches from stdin
🔀 Auto-detects #Jujutsu and #Sapling checkouts and uses native revsets; can be set as pager for #Git

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

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

🤖 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

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

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

🤖 /lfg runs the whole pipeline hands-off: plans, works, simplifies, runs code review and applies fixes, executes browser tests, commits, pushes, opens a PR and watches CI with a bounded repair loop
🧩 33 skills grouped into core loop, on-demand helpers (/ce-debug, /ce-ideate, /ce-explain, /ce-optimize), #git workflow, testing/design and collaboration

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".

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

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

{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.

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

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

🎨 Tools: ReadFile, Glob, SearchCode, EditFile, WriteFile, RunArtisan, RunTests, RunPint, RunShell, plus observability for logs, read-only SQL, routes, git diffs, #Telescope entries, #Sentry issues and #GitHub

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

Periodic git-extra-commands announcement
#git helper scripts and other git-related resources I've accumulated over the years.
You don't need a ZSH framework to use it - the framework code just adds the repo's bin directory to your PATH automatically.
#git #homelab #selfhosting #sre #devops #swe