heptapod (@heptapod@fosstodon.org)
#heptapod 18.2.2 released, bumping #gitlab to the 18.2.6 regular patch/security version Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.2.2/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
Show Original Post
teajaygrey (@teajaygrey@snac.bsd.cafe)
Thank you for the quick fix!
I submitted a Pull Request to update MacPorts' GoT to 0.118.1 here:
https://github.com/macports/macports-ports/pull/29307
2 of 3 GitHub Continuous Integration checks have passed so far (which is probably a good indicator the third will pass, eventually?).
It's up to someone else with commit access to merge it!
#GoT #GameOfTrees #MacPorts #VersionControl #OpenSource #macOS #Git
Show Original Post
GLubrano (@GLubrano@mastodon.uno)
Git: I repository
Inizializzazione di un repository locale e Clonazione di un repository remoto
https://giovannilubrano.blogspot.com/2025/09/git-i-repository.html
Show Original Post
post (@post@programming.dev)
Some thoughts on personal git hosting
https://programming.dev/post/37211057
Show Original Post
hn50 (@hn50@social.lansky.name)
Some thoughts on personal Git hosting
Link: https://shkspr.mobi/blog/2025/09/some-thoughts-on-personal-git-hosting/
Discussion: https://news.ycombinator.com/item?id=45157425
Show Original Post
GripNews (@GripNews@mastodon.social)
🌗 關於個人 Git 主機託管的幾點思考
➤ 探索個人 Git 託管的挑戰與可能性
✤ https://shkspr.mobi/blog/2025/09/some-thoughts-on-personal-git-hosting/
作者 Terence Eden 為了實現個人專案的去中心化，嘗試將專案從 GitHub 遷移到個人託管的 Git 服務。他目前使用 PikaPod 託管 Gitea 服務，但面臨著網路效應、協作性（如 Pull Request 的發送與尋找）、程式碼的可發現性、管理上的繁瑣以及贊助等挑戰。作者最終計劃將較受歡迎或有贊助的專案保留在 GitHub，較小的專案則移至個人 Git 服務，並尋找類似 Forgejo 的託管方案。
+ 我完全理解作者的顧慮，GitHub 的網路效應確實是一個巨大的門檻。我也曾想過自建 Git 服務，但 CI/CD 的整合始終是個難題。
+ PikaPod 聽起來是個不錯的選擇，但如果能有更簡單的方案，或是像 Radicle 這樣的 P2P 解決方案，也許更能實現去中心化的目標。
#軟體開發 #開源 #Git #去中心化 #託管
Show Original Post
RosaCtrl (@RosaCtrl@social.vivaldi.net)
TIL about #Git’s difference between current and simple default push behaviour. The question is why does the concept of tracking a branch exist?
Show Original Post
jbz (@jbz@indieweb.social)
Some thoughts on personal git hosting | Terence Eden
｢ I'm looking at moving my personal projects away from GitHub. I already have accounts with GitLab and CodeBerg - but both of those sites are run by someone else. While they're lovely now, there's nothing stopping them becoming as slow or AI-infested as GitHub.
So I want to host my own Git instance for my personal projects ｣
https://shkspr.mobi/blog/2025/09/some-thoughts-on-personal-git-hosting/
Show Original Post
clonbg (@clonbg@masto.es)
Hacer que git no pida contraseña https://myblog.clonbg.es/hacer-que-git-no-pida-contrasena/ #Git #Seguridad https://clonbg.es
Show Original Post
amedee (@amedee@lou.lt)
Lost a commit after its branch got deleted on GitHub? I did too. Cloning didn’t help. `git fsck` didn’t help. But `git fetch origin ` saved the day. Turns out even GitHub forgets things—unless you ask *really* nicely. Full story on the blog. 🧟♂️ #git #programming
Show Original Post
%f0%9f%a7%9f%e2%99%82%ef%b8%8f-resurrecting-a-dead-commit-from-the-github-graveyard (@%f0%9f%a7%9f%e2%99%82%ef%b8%8f-resurrecting-a-dead-commit-from-the-github-graveyard@amedee.be)
🧟♂️ Resurrecting a Dead Commit from the GitHub Graveyard
There comes a time in every developer’s life when you just know a certain commit existed. You remember its hash: deadbeef1234. You remember what it did. You know it was important. And yet, when you go looking for it... 💥 fatal: unable to read tree Great. Git has ghosted you. That was me today. All I had was a lonely commit hash. The branch that once pointed to it? Deleted. The local clone that once had it? Gone in a heroic but ill-fated attempt to save disk space. And […]
Show Original Post
stsp (@stsp@bsd.network)
(Self-)hosting costs real money:
https://opencollective.com/gothub/expenses/
We are about to send more than €2k, almost half our existing @gothub funds, to hosting companies. (This includes horrendous one-time setup fees which I somehow managed to negotiate down by 50%.)
When users rely on hosted services without paying for them, the costs are somehow being offset by someone else.
If you are moving your #git repositories to @Codeberg as so many of you seem to be doing now (good!), please donate regularly to keep them afloat long-term.
@gothub requires payments (as small as we can reasonably make them) to ensure that the ship won't sink as long as the costs can be offset by people using service or contributing to the fund. In this model, the more users we get, the cheaper we can get by spreading the costs.
Show Original Post