dan (@dan@m.danq.me)
I've spoken to two friends now whose (different) employers are trying to monitor which #developers are actively using #AI, as if doing so is some kind of metric for success.
So I wrote an (only slightly tongue-in-cheek) #git post-commit hook that spoofs the records their AI agents might have made, so management can't tell that they're not drinking the kool-aid.
(Obviously it'd be better if my friends could just openly say "nah, I produce better code without AI", or else have a different job with management that respects them, but until that happens...)
🔗 https://danq.me/ai-agent-logging
Show Original Post
kpcyrd (@kpcyrd@chaos.social)
@Diziet It feels like sha256 #git is grid-locked between "there's rough edges because there have been very few eyes on this", "very few people try because Github doesn't support it", "Github doesn't support it because there's no demand", "Not enough people are sassy enough to deliberately break Github compatibility" 🥲
Show Original Post
post (@post@programming.dev)
Git Rev News Edition 132 (February 28th, 2026)
https://programming.dev/post/46629716
Show Original Post
lwn (@lwn@fedi.lwn.net)
[$] Free software needs free tools
One of the contradictions of the modern open-source movement is that projects which respect user freedoms often rely on proprietary tools that do not: communities often turn to non [...]
https://lwn.net/Articles/1060649/ #LWN #Linux #Git
Show Original Post
habr (@habr@zhub.link)
От CI к GitOps: Bootstrap Namespaces в Kubernetes
Привет, Хабр! Меня зовут Никита Чубаров. По трудовому договору я инженер-эксперт по разработке и сопровождению сервисов, а по факту DevOps-инженер с фокусом на доставку в платформенных командах, которые поставляют общие решения для десятка дочерних команд. Со временем эта доставка перестала быть прозрачной и предсказуемой, и всё больше напоминала космолёт, в котором пилот перед каждым запуском вручную подключает провода, проверяет давление в контурах и по списку нажимает десятки кнопок. Пока запусков мало, это ещё можно представить, но когда их становится сотни, а кораблей — десятки, такая схема быстро превращается в источник ошибок и выгорания. Примерно в таком состоянии у нас находился Bootstrap Namespaces. В статье я расскажу, как мы прошли путь от сложной CI-оркестрации к декларативному управлению Bootstrap Namespaces через Argo CD и GitOps, какие проблемы это позволило убрать и какие новые ограничения пришлось принять.
https://habr.com/ru/companies/raiffeisenbank/articles/1001782/
#gitops #argo_cd #applicationset #bootstrap #helm #cluster #git #generator #infrastructure_as_code #app_of_apps
Show Original Post
smartgit (@smartgit@techhub.social)
Because we rely heavily on cloud to host our #code, it’s easy to think of them as the absolute source of truth.
But structurally? Git doesn't care about the cloud ☁️🚫
Every time you clone a #Git repo, you are downloading a full-fledged, 100% complete backup of the entire project history.
#SmartGit embraces this local-first power, giving you full control over your repo whether you have a Wi-Fi or not.
Have you ever had to keep working entirely offline during a server outage? 🌍💻
Show Original Post
kechpaja (@kechpaja@social.kechpaja.com)
Some time ago, I toyed with the "crazy" idea the the ideal name for the primary branch in a #Git repo wasn't _master_, _main_, or _trunk_, but rather _/_ — becuase then you could treat it as the root of a directory tree, with branches named as if they were subdirectories under the branch they were branched from.
I messed around a bit with this idea, and it turns out that Git disallows _/_ as a branch name (because branch names are stored as filesystem paths under `.git/refs/heads`).
Now I'm considering something unironically doesn't sound crazy at all: name the primary branch _after the short name of the project_, and then name branches according to the tree structure mentioned above. That would get you such branches as:
```
example-proj (primary branch tracking prod)
example-proj/staging (branch tracking staging env)
example-proj/develop (main development branch)
example-proj/develop/<feature> (feature branch)
```
It would look weird at first and require a tiny bit more typing (which can be alleviated with autocomplete), but it also feels _right_ in a certain way.
I will need to play around with this more.
Show Original Post
sayzard (@sayzard@mastodon.sayzard.org)
Avi Chawla (@_avichawla)
Postman이 API 작업을 개발자 워크플로에 새롭게 통합하는 재설계를 발표했습니다. 그동안 컬렉션은 별도, 코드베이스는 Git으로 버전 관리되고 CI는 브랜치/PR에서 동작해 왔으나, 이번 변경으로 API 스펙·컬렉션·테스트와 코드/버전관리/CI의 연계가 강화되어 개발 흐름 내에서 API 작업을 더 자연스럽게 다룰 수 있게 됩니다.
https://x.com/_avichawla/status/2028720380379361634
#postman #api #developer #workflow #git
Show Original Post
tobru (@tobru@mstdn.social)
Git in Postgres
"Instead of using git as a database, what if you used a database as a git?"
Link: https://nesbitt.io/2026/02/26/git-in-postgres.html
#linkdump #blogpost #database #forgejo #git #postgresql
Show Original Post
stephenblum (@stephenblum@mastodon.social)
Mobile works now, cleanup next, commit to main, push today.
Show Original Post
stephenblum (@stephenblum@mastodon.social)
Too many deletions, restore needed code, explain changes before merging.
Show Original Post
lwn (@lwn@fedi.lwn.net)
[$] The ongoing quest for atomic buffered writes
There are many applications that need to be able to write multi-block chunks of data to disk with the assurance that the operation will either complete successfully or fail altoget [...]
https://lwn.net/Articles/1060063/ #LWN #Linux #kernel #Git #PostgreSQL #PostgreSQL #XFS #BPF #io_uring
Show Original Post