I really have to write a #blog post titled "I hate rebase-merge workflows"
#git #softwaredevelopment #workflow #github
📜 Latest Top Story on #HackerNews: Show HN: I replaced vector databases with Git for AI memory (PoC)
🔍 Original Story: https://github.com/Growth-Kinetics/DiffMem
👤 Author: alexmrv
⭐ Score: 29
💬 Number of Comments: 5
🕒 Posted At: 2025-08-21 06:20:11 UTC
🔗 URL: https://news.ycombinator.com/item?id=44969622
#ai #git #hackernewsbot #hackernews #news #bot
I replaced vector databases with Git for AI memory (PoC)
https://github.com/Growth-Kinetics/DiffMem
#HackerNews #AI #Memory #Git #Vector #Databases #PoC #Growth #Kinetics
Your main #quarto website repo shouldn't be a storage unit for every plot you've ever made 📦
#git #submodules: Give your figures their own space, keep your repo fast
I ran into a problem today where I needed to use different protocols / authentications methods / URLs for pulling (fetch) from and pushing to a #git repo.
It turns out that it's relatively straight forward to do:
--8<--
# git remote set-url --push ${REMOTE} ${URL}
-->8--
I was using a Deployment Key to for read-only pull (fetch) from a private GitHub repo, but I needed the ability to authenticate as myself to be allowed commit and push. -- Automation can pull (fetch) from the repo but is prevented from writing to it.
After changing the URL line in the .git/config file a few times, I searched and found that there is an easy way to have different protocols / authentication methods / URLs for pull (fetch) and push.
I thought that it might be the case, as I'd seen that `git remote -v` listed the same remote twice with the difference being `(fetch)` and `(pull)` on the two lines.
--8<--
# git remote -v
${REMOTE:-origin} ${URL} (fetch)
${REMOTE:-origin} ${URL} (push)
-->8--
🌗 程式碼審查可以更進步
➤ 從 Git Commit 體驗程式碼審查的新可能
✤ https://tigerbeetle.com/blog/2025-08-04-code-review-can-be-better/
本文探討了現有程式碼審查工具（特別是 GitHub）的不足之處，作者嘗試開發名為 `git-review` 的工具，將審查意見直接嵌入程式碼，並以單一 Git Commit 的形式管理，以期改善審查效率。儘管此方法在技術層面上展現了優勢，例如本地化審查、直接修改程式碼並獲得開發環境的支援，但實際執行時面臨許多細節上的挑戰，包括版本衝突、強制推送的摩擦以及與 Git 核心功能的潛在不相容。最終作者回到基於網頁的審查方式，並期望未來能有更完善的解決方案。
+ 作者的想法很有趣，將審查意見視為 Git Commit 的一部分，這確實能帶來更順暢的本地開發體驗。但看來實作細節纔是真正的難關。
+ 我也曾遇到 GitHub 審查介面延遲的問題，非常期待有人能提出真正解決這個痛點的方案。將審查與版本控制更緊密結合是個好方向。
#程式碼審查 #Git #開發工具
woh, jujutsu is already leaking into git
https://lore.kernel.org/git/20250819-b4-pks-history-builtin-v1-0-9b77c32688fe@pks.im/
that's amazing. kudos to martin and his mates
Interesting discussion on Lobsters about Code review.
I like this workflow:
https://lobste.rs/s/zxglnn/code_review_can_be_better#c_zg5hf4
Interesting discussion on Lobsters about Code review.
I like this workflow:
https://lobste.rs/s/zxglnn/code_review_can_be_better#c_zg5hf4
Hacer push a varios remotes de Git al mismo tiempo
https://blog.thalskarth.ar/push-varios-git-remotes/
🐱👤 Oh no, the #anime #catgirls have rebelled and are now the gatekeepers of the #Linux kernel! Who knew that protecting the web from AI meant enlisting #kawaii #avatars to thwart your #git clones? 🤖 Seriously, at this point, even Tux is rolling his eyes. 🙄
https://lock.cmpxchg8b.com/anubis.html #rebellion #clones #HackerNews #ngated