GripNews (@GripNews@mastodon.social)
🌘 pgit：如果你的 Git 歷史記錄是一個 SQL 資料庫會怎樣？
➤ 當版本控制遇上 SQL：資料庫驅動的開發歷史洞察
✤ https://oseifert.ch/blog/building-pgit
pgit 是一個創新的版本控制 CLI 工具，它徹底顛覆了傳統 Git 將資料存於檔案系統的作法，改以 PostgreSQL 作為核心儲存引擎。透過整合自行研發的 `pg-xpatch` 擴充功能，pgit 實現了透明的自動化差異（Delta）壓縮，在有效節省儲存空間的同時，讓用戶能直接使用 SQL 語法查詢深度的代碼變更歷史、檔案耦合度與貢獻指標，打破了傳統 Git 操作僅能依靠命令列輸出解析的限制。
+ 這太驚人了！以前要分析這種代碼耦合度或熱點檔案，總是得寫一堆複雜的 shell script 來處理 git log，現在直接下 SQL 就能得到結果，效率提升了好幾個檔次。
+ 雖然在部分跨檔案高度相似的專案上，git 的 packfile 格式仍有優勢，但 pgit 能在提供 SQL 強大查詢
#資料庫技術 #Git 工具 #資料壓縮 #PostgreSQL #開源軟體
Show Original Post
frontenddogma (@frontenddogma@mas.to)
My First Git Commit, by @ddbeck:
https://ddbeck.com/notes/first-git-commit/
Show Original Post
ngate (@ngate@mastodon.social)
🚀🎩 Oh look, someone decided that #Git wasn't complex enough and thought, "Let's slap #PostgreSQL on it!" 😂 Now you can turn your version control into a hipster's SQL #nightmare, while your codebase health is judged by an #AI with the attention span of a goldfish. 🙄💾
https://oseifert.ch/blog/building-pgit #hipster #tech #humor #HackerNews #ngated
Show Original Post
h4ckernews (@h4ckernews@mastodon.social)
Pgit – A Git-like CLI backed by PostgreSQL
https://oseifert.ch/blog/building-pgit
#HackerNews #Pgit #Git #PostgreSQL #CLI #TechNews
Show Original Post
ct_Magazin (@ct_Magazin@social.heise.de)
c’t-Workshop: GitLab CI im Praxiseinsatz
GitLab CI/CD verstehen und anwenden: Der Workshop zeigt, wie Sie Pipelines für Builds, Tests und Deployments strukturieren und effizient im Team nutzen.
#ContinuousDelivery #ContinuousIntegration #Git #IT #Softwareentwicklung #news
Show Original Post
2026 (@2026@blog.narf.ssji.net)
Git: ignoring temporary changes
https://blog.narf.ssji.net/2026/03/18/git-ignoring-temporary-changes/How to tell git that a change SHOULD NOT be considered?
tl;dr: git update-index –assume-unchanged
#Git
Show Original Post
developer_deku (@developer_deku@mastodon.social)
create version(editing history)
we should create the version(editing history) to manage source code on git repository. we introduce how to create version(editing history).
https://deku.posstree.com/en/git/create-stage/
Show Original Post
developer_deku (@developer_deku@mastodon.social)
버전(변경이력) 생성
git의 저장소(Repository)로 버전 관리를 하기 위해 버전(변경 이력)을 생성하는 방법에 대해서 알아봅니다.
https://deku.posstree.com/ko/git/create-stage/
Show Original Post
developer_deku (@developer_deku@mastodon.social)
バージョン生成
gitのリポジトリ(Repository)でバージョン管理するためにバージョン(変更履歴)を生成してみましょう。
https://deku.posstree.com/git/create-stage/
Show Original Post
forge (@forge@gts.gitroot.dev)
Just pushed THE breaking change of the next version.
Decoupling commit signing from SSH push keys to give you more flexibility.
• No more auto-generated `.gitroot/init.sh` or `.gitroot/allowed_signers` by default.
• Push unsigned commits or from other authors (hello, easy rebases!).
Want the old strict behavior back? Install the stigma plugin:
✅ Manages `.gitroot/allowed_signers` for you.
⚠️ Warns on unsigned commits.
❌ Errors on invalid signatures.
More details https://gitroot.dev/CHANGELOG.html
#Git #DevOps #OpenSource #CodingTips
Show Original Post
PacoVelobs (@PacoVelobs@mamot.fr)
Not gonna lie, a few years ago when I eared @robinm asking for a built-in plugin manager in #vim / #nvim, I was not convinced.
Why? Because I thought it was already the case. `pack/{opt,start}` has been around for quite a while now and I used #git #submodules to have a portable configuration.
Since then, I've used various plugins manager. They're handy but don't offer much more than the built-in.
And now, back to sugar-coated basics: https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack.
I now agree with @robinm.
Show Original Post
bradwilson (@bradwilson@mastodon.social)
@TeaDrivenDev Okay, I'm done with worktrees. They're just not fully baked in terms of tooling. #git #worktree
Show Original Post