git Timeline - FediScanner

14.08.2025 17:19
GripNews (@GripNews@mastodon.social)

🌘 Jujutsu 與 Radicle 的結合：打造無縫協作開發流程
➤ 打造下一代去中心化協作開發體驗
✤ https://radicle.xyz/2025/08/14/jujutsu-with-radicle
本文分享了作者如何將 Jujutsu（jj）這款 Git 替代工具與 Radicle 結合使用，以優化開發和協作流程。作者透過詳細介紹 Jujutsu 在版本管理上的靈活性，以及 Radicle 在去中心化協作方面的優勢，說明瞭如何將兩者無縫整合。文章從 Git 設定、Radicle 的推拉操作，到 Jujutsu 的提交、編輯、重寫等核心功能，逐步展示瞭如何建立一套高效、幾乎無分支的開發工作流程。
+ 這個結合聽起來很令人興奮！Jujutsu 的彈性加上 Radicle 的去中心化，感覺能解決不少現有協作工具的痛點。
+ 感謝作者詳細的技術分享，特別是 `.git/config` 的部分，讓我更清楚如何讓 Git 與 Radicle 配合。Jujutsu 的 `jj new -B` 功能也很實
#版本控制 #開發工具 #開源 #Git #Jujutsu #Radicle

Show Original Post

Report

14.08.2025 15:56
radicle (@radicle@toot.radicle.xyz)

Jujutsu + Radicle = ❤️

Follow along with Fintan as he details how he put his Git workflow into submission with Jujutsu 🤼

https://radicle.xyz/2025/08/14/jujutsu-with-radicle

#jj #jj-vcs #jujutsu #git #radicle #vcs

Show Original Post

Report

14.08.2025 15:47
kingthorin_rm (@kingthorin_rm@infosec.exchange)

Hey git do we really need to answer the same question over and over and over and over, can't these be batched/queued and "Yes to All", "No to All" options added?

(On Winblows systems is git ever able to remove the packs during this operation?)

#git #gitpro

Show Original Post

Report

14.08.2025 14:04
larsmb (@larsmb@mastodon.online)

It is 2025.

I have been using Linux as my only driver since 1994.

I am only now¹ starting to finally put all my dotfiles and other configuration data for my home directory under version control².

² #git & #forgejo
¹ I mean, that's not quite true, I've done it before once: $Id: .bashrc,v 1.2 1999/01/30 21:47:51 lmb Exp $

Show Original Post

Report

14.08.2025 14:04
AAD_OeAW (@AAD_OeAW@fedihum.org)

Hello #Git experts,

What's the best practice in this case:

- we have two branches (main, dev)
- we exclusively work on dev (both creating new & changing old data)
- every now & then, we need to merge dev into main
- after the merge, main is ahead of dev by 1 commit (the merge commit)

Currently, we go on by merging main back into dev, so that dev does not stay behind main, before continuing work on dev.

Is this good (or, at least, okay) practice, or should we use different merge strategies?

Show Original Post

Report

14.08.2025 13:36
heptapod (@heptapod@fosstodon.org)

#heptapod 18.2.0 (final) released, based on #gitlab 18.2.2 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.2.0/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial