I'm finally moving over to Radicle (https://radicle.xyz) instead of switching to another centralized code forge (like GitHub, GitLab, Codeberg, etc.). I definitely love the idea behind a #P2P code forge and I'm hopeful for Radicle's future, but I do have some reservations starting off:
1) Despite talking a lot about freedom and privacy in the tutorial, the group building Radicle (https://radworks.org/) is planning to sell hosting and make a profit via an Ethereum-based cryptocurrency (https://www.tally.xyz/gov/radworks) as well as NFTs and smart contracts. Some big Libertarian red flags there.
2) At some point there was a Swiss nonprofit "Radicle Foundation", but this now seems to be a for-profit venture (see https://radicle.xyz/history). I wish it could just be a nonprofit.
3) In the user guide chapter on private repos (https://radicle.xyz/guides/user), it says that I need to use a public DNS address trusted seed node to share the repo. I understand there's no DHT here, but I hope it's not too much of a pain to run this over my local network instead of the internet. (And yeah, I know I can use git locally, I just want to test Radicle locally.)
Overall, I think that if radworks turns out to be evil it will be a way easier transition to fork Radicle than it has been to leave GitHub, but I still wish I didn't have to worry.
Something I missed / overlooked previously. The instructions to easily mirror your Github repos to #Codeberg
Thanks for the tip by @jwildeboer
https://codeberg.org/Recommendations/Mirror_to_Codeberg#github-mirror
Today's been one of those days where I wish we were using anything other than #perforce for version control. This thing is broken beyond belief. Working on several changelists? Sure, but don't create new files, shelving them and reverting the changelist doesn't remove the newly added file from the filesystem. Which breaks #ceedling's automatic test discovery. The work around is to rename the test_* file with some other prefix manually. It sucks.
#versioncontrol
Can I have some recommendations for the privacy respecting web-based platform for version control and repository management? Ditching Github once for all
Nous aurons le plaisir d’accueillir Maëlle Salmon @maelle, Research Software Engineer, qui partagera son expertise sur Git.
Vendredi 11 avril à 12H CEST
#Zoom
Plus de détails et RSVP : https://www.meetup.com/rladies-paris/events/307063402/
#RStatsFr #RStats #RLadies #VersionControl #Git @RLadiesGlobal
jj (aka jujutsu), the git-compatible version control system, just released version 0.27.0.
The package for @opensuse was adapted, tested and worked out fine. Will soon be available in #Tumbleweed!
For starters, I can highly recommend Steve Klabnik's tutorial:
https://steveklabnik.github.io/jujutsu-tutorial/
How I spent the last couple of weeks (part 10? 11?):
I used jj aka jujutsu a lot. Basically I use it for all of my repos that do NOT have git submodules.
I really like the workflow, although my muscle memory leads me to type git commands sometimes. And I need to come up with a set of aliases like have for git. "g" for "git status", "gp" for "git push", that kinda thing.
I am looking forward to the further developement of jujutsu and can hardly wait until it includes submodule support!
Preparing the feedback cards (with additional information about the content of the workshop) for our upcoming @thecarpentries - workshop about #git in Berlin. We still have open seats for any one interested in #versioncontrol https://m.politze.net/2025-02-17-rdade/
The workshop is organized by @RDA_Association Deutschland and conducted by @dkz2r
What if the classic residential environment of Medley Interlisp met the modern file based Git? The GITFNS tools are a step at bridging these worlds.
Here the PRC command (PR Comparison) shows in side by side windows the diffs of a Lisp function between two branches of Medley's repo. The smaller window at left is a list of PRs. More details in the GITFNS documentation:
https://files.interlisp.org/medley/lispusers/GITFNS.TEDIT.pdf
Has someone attempted to build a #CodeReview tool that relies more on #git itself like using git notes and git trailers and such?
For anyone interested in Git or version control, I highly recommend Scott Chacon's talks. Yes, he talks fast, but damn, that man knows git in and out and always has some things up his sleeve that you did not yet know about Git...
So You Think You Know Git - FOSDEM 2024
https://yewtu.be/watch?v=aolI_Rz0ZqY
Scott Chacon - So you think you know GitAdvanced Git Tips and Tricks - DevWorld 2024
https://yewtu.be/watch?v=e6ZI6AmlHN4
And for the hardcore git fans, there is an older talk where he use git plumbing commands to create commits and objects and whatnot. Very very deep dive but also very nice to get an understanding how git works under the hood...
The next person who advocates that "Perforce is more user friendly than Git and better for artists." to my face will get a custard pie in response. It really isn't any different to any other VCS is terms of complexity and arguing that it is "user friendly" compared to git is just lies.
Git's Time Machine: A Guide to Fixing Your Mistakes Like a Pro
Git can be a daunting tool for developers, often leading them into a maze of confusion and frustration. But fear not! This guide reveals some of the most common pitfalls and how to escape them with a ...
https://news.lavx.hu/article/git-s-time-machine-a-guide-to-fixing-your-mistakes-like-a-pro