#heptapod 18.8.1 released, bumping GitLab to the patch/security release 18.8.5 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.8.1/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
#heptapod 18.7.5 released, bumping #gitlab to the regular patch/security release 18.7.5 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.7.5/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
git worktreeとCursorで爆速並列開発！複数ブランチを同時に作業するワークフロー
https://qiita.com/sugumura/items/232710ff53c87c10eaba?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#qiita #Git #初心者向け #cursor #GitWorktree
@satobi No, absolutely not. Because on a main branch it's often useful to maintain invariants like, the branch tip should always compile and pass tests, and each "step" from one main branch tip to the next should represent a coherent functional change in the software (e.g. a feature or bug fix), but when reviewing the history of the code it's often useful to see each functional change broken down in more granularity than that, so that you understand the story of how the change was made. (For example, in test driven development, you might write the tests in one step and write the code that makes them pass in a later step.) You can only get the benefits of both approaches if you don't squash commits.
Though, when I'm working I do make tiny commits like "fix", "WIP on thing", "checkpoint - some tests pass", and _those_ I do squash, but I usually do that before even pushing the branch. Those tiny incremental commits are just "implementation details".
Game of Trees 0.123 released https://www.undeadly.org/cgi?action=article;sid=20260226054524 #openbsd #gameoftrees #got #git #gothub #development #programming #versioncontrol #sourcecontrol
Git Blame it on the rain
#BlameASongOrPoem
#HashtagGames
#git
🔍 Desmistificando o Debate Git vs. GitHub: Entendendo as Principais Diferenças 🖥️🔗
Git e GitHub são frequentemente confundidos, mas possuem funções distintas no mundo do desenvolvimento. Descubra as diferenças essenciais entre eles e como cada um pode beneficiar seus projetos!
👉 Saiba mais no blog: https://nova.escolalinux.com.br/blog/desmistificando-o-debate-git-vs-github-entendendo-as-principais-diferenas?utm_source=dlvr.it&utm_medium=mastodon
#Git #GitHub #Desenvolvimento #Tecnologia #CódigoAberto
Git’s Magic Files, by @andrewnez:
https://nesbitt.io/2026/02/05/git-magic-files.html
Support period lengthened for the 6.6, 6.12, and 6.18 kernels
https://lwn.net/Articles/1060271/ #LWN #Linux #kernel #Git
queuing merges in jujutsu
https://pauladamsmith.com/blog/2026/02/introducing-jjq-a-local-merge-queue-for-jj.html
Git Crash Course (Tomorrow, 26.02.26):
Link: https://thealternative.ch/?eventId=91
Title: Git Crash Course
Speaker: Valentin Kaas
Place: #ETH HG D 7.1
Start Time: 18:15
End Time: 20:00
Date: 2026-02-26
Description:
#Git is the state-of-the-art version control system, taking away the pain of continuously changing file versions. Keep track of who changed what, when and why, and revert changes easily.
#GitLab allows you to save the files to the cloud, giving you a secure backup location and enabling easy collaboration. Never lose your files again, and coordinate changes in even bigger projects.
This course gives you a fast theoretical overview over all the concepts surounding Git and it will show you how to use Git.