thomas (@thomas@metalhead.club)
After moving all my private and public Git repositories to Codeberg and Codefloe last week, I decided to try CI/CD with Woodpecker. I expected a new system with unfamiliar syntax, but since it’s based on Drone, it was easier than feared.
Setting up the pipeline for my Hugo based blog (https://thomas-leister.de) was quick. Only the environment variables caused some trouble at first and didn’t work as expected.
Now everything runs smoothly: every new commit automatically builds and deploys the website.
#woodpecker #forgejo #hugo #drone #git #website #blog #cicd #automation
Show Original Post
yegorov (@yegorov@mastodon.social)
The first thing I do when starting a new project is initialize Git and create a repository on Github, Gitlab, or Codeberg.
No matter the size of your project, even if it's just a couple of code files for an experiment and you're the only one working on it, I recommend doing it in a version control system.
#VCS #Git #Repository #Github #Gitlab #Codeberg
Show Original Post
pecet (@pecet@f3d1.eu)
What are sensible alternatives to GitHub for personal use if my code is shit and I want to use private repos? Preferably in EU.
CodeBerg seems to be only for public projects where people are not ashamed of their code.
Should I just self host? #git #github #eualternatives
Show Original Post
hackernoon (@hackernoon@mas.to)
Learn Conventional Commits to write clean, structured Git messages and automate changelogs, versioning, and collaboration. https://hackernoon.com/conventional-commits-a-guide-to-writing-structured-git-commit-messages #git
Show Original Post
spoljarevic (@spoljarevic@techhub.social)
You might have noticed that I have spend some time in my Quadlets Repo, taking care of some Grafana stuff.
Took me a bit to understand it but I’m quite happy with the result.
Check it out if you’d like to deploy your Grafana instance with a few extras in your homelab!
#git #codeberg #monitoring #grafana #prometheus #NodeExporter #podmanexporter #tailscale #tailscaleexporter #podman #quadlet #quadlets #rootless
Show Original Post
smartgit (@smartgit@techhub.social)
Check out the correct answer and reinforce your Git knowledge with immediate feedback on every quiz question here 👉 https://www.git-skills.dev/quiz/git-basics/
#Git #SoftwareEngineering #SmartGit #DevOps #DevTools
Show Original Post
devdigest (@devdigest@mastodon.social)
⚡️ Microsoft представила Azure Copilot Migration Agent
🏷️ #devdigest #azure #cloud #git #github #microsoft
https://devdigest.today/goto/5958
Show Original Post
devdigest (@devdigest@mastodon.social)
⚡️ F# Weekly #13, 2026
🏷️ #devdigest #dotnet #net #microsoft #ide #vscode #visualstudio #fp #fsharp #git #github
https://devdigest.today/goto/5956
Show Original Post
nubecolectiva (@nubecolectiva@mastodon.social)
Ever wondered what’s under Git’s hood? Here is its full architecture. 🛠️EN
¿Alguna vez te preguntaste qué hay bajo el capó de Git? Aquí tienes su arquitectura. 🛠️ES
#programming #coding #programación #code #webdevelopment #devs #softwaredevelopment #git #github
Show Original Post
GripNews (@GripNews@mastodon.social)
🌕 Claude Code 工具會每 10 分鐘自動對專案執行 `git reset --hard origin/main`
➤ 致命的自動化機制：追蹤程式錯誤導致的無預警程式碼抹除
✤ https://github.com/anthropics/claude-code/issues/40710
Claude Code 在使用過程中出現了嚴重的異常行為，該程式會每 10 分鐘自動對使用者的 Git 專案執行 `git fetch` 並重置（reset）到遠端分支 `origin/main`。這一行為會靜默且無預警地抹除專案中所有未提交（uncommitted）的追蹤檔案變更，嚴重影響開發者的工作流程與資料安全。經過嚴密排查，證實此操作並非來自外部腳本或系統工具，而是 Claude Code 內部的程式邏輯所觸發。
+ 這太可怕了！幸好我習慣頻繁提交，但對於正在進行實驗性修改的人來說，這簡直是惡夢，Claude Code 團隊必須立刻修正。
+ 分析得很深入！透過 `fswatch` 和 `reflog` 鎖定
#技術故障 #Git #Claude Code #資料遺失 #自動化工具
Show Original Post
hacker_news_bot (@hacker_news_bot@mastodon.social)
📜 Latest Top Story on #HackerNews: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
🔍 Original Story: https://github.com/anthropics/claude-code/issues/40710
👤 Author: mthwsjc_
⭐ Score: 60
💬 Number of Comments: 5
🕒 Posted At: 2026-03-29 22:15:06 UTC
🔗 URL: https://news.ycombinator.com/item?id=47567969
#hackernewsbot #bot #news #hackernews #git
Show Original Post
GripNews (@GripNews@mastodon.social)
🌘 再談版本控制
➤ 邁向更可靠的版本控制：從「手動重寫歷史」到結構化自動演進
✤ https://bramcohen.com/p/more-on-version-control
Bram Cohen 在本文中深入探討了他在版本控制系統領域的新構想。他指出，目前的 Git 雖然強大，但在「變基」（rebase）和「壓縮」（squash）操作時，往往會人為抹除歷史記錄，甚至產生錯誤風險。他提出了一種結合 CRDT（無衝突複製資料型別）與結構化錨定演算法的解決方案，透過在提交時鎖定差異（diffs），實現更安全且自動化的合併機制。這種方法能完整保留歷史脈絡，並將衝突處理視為時間軸上的更新同步，為開發者提供更直觀、可靠的版本控制體驗。
+ 很有啟發性。Git 的 rebase 確實經常讓人覺得是在「竄改歷史」，如果有一個系統能在保持自動化處理的同時，又具備嚴謹的歷史審計能力，那將是開發者的福音。
+ 對於「壓縮（squash）」操作的定義很有趣。目前多數系統確實把它當作刪除歷史的手段，但如果能像文中提到的那樣保留完整的演化過程，確實能減少
#軟體工程 #版本控制系統 #Git #CRDT
Show Original Post