> Deleted all the forks I had on GitHub, moved the very few repos I care about over to Codeberg
I believe moving over to #Codeberg is a big improvement over relying on #GitHub (which, as #SourceForge once was, is the center of gravity for FOSS projects' development).
I closed all my repos on GH some years back. I kept one or two repos on #BitBucket for years, but they were basically dead. When BB rid itself of #Mercurial ( #hg ) and switched solely to #git, I took advantage of the opportunity to close my account there.
That said, large numbers of people moving en mass from GitHub to Codeberg would just move the problem to a different platform. The problem being people rely heavily on a centralized service.
As for GitHub, I still have my account, and with job-hunting, I really need to put something there. Seriously, I have had some places send rejection notices because they couldn't see any evidence (on GitHub) that I knew anything about the job. But I really only want GH to be a secondary mirror of a main repo hosted elsewhere.
Most of what I do goes into my #Fossil repo, but I'm also trying to use #Darcs, #Breezy, #Pijul, and #Hg enough to be able to fairly say which ones work best for me.
You'll notice that #Git is not in that list. I'm having to use git whenever I deal with other people's code projects, so I already know that it isn't tailored for my needs.
I also think that our #code-hosting solutions needn't presume #git. All of #hg, #fossil, #darcs, #pijul, #brz can be viable depending on the project & organization.
> --fixup=reword:<commit> creates an "amend!" commit which replaces the log message of <commit> with its own log message but makes no changes to the content of <commit>.
@geniusmusing I find #git to be too big and complex for my needs (and arguably for most projects). I know it โwonโ and even some projects that formerly used another #VCS ( such as Mercurial #hg, #darcs, Bazaar #bzr / Breezy #brz ) are switching.
In the plans: a very limited #Kallithea install (with git and Mercurial) and #Fossil for Federati ... when I have more funds and energy to devote to getting it going on its own VPS.
So, next bottleneck in my superscript: I have a sequence of nice commands that git pull and build apps. However i want to build apps just when git pull pulls something new. i found this piece of code but seems not working for me:
cd ~/app_builds/APP1; changed=0 git remote update && git status -uno | grep -q 'Your branch is behind' && changed=1; if [ $changed = 1 ]; then echo "Updating and building"; COMMANDS FOR BUILD else echo "Up-to-date - skipping"; fi
I think yโall know I favor the #Fossil #SCM / #DVCS over #Git (though Iโm giving #Mercurial ( #Hg ) another look as well. Iโm resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
@musicman Yes, I think #git is overly complicated for most projects' needs, but it has mindshare, so people often demand it when another VCS would be more appropriate. It'd be great if transitioning from one to another was a well-understood problem, but it isn't.
Is that #Emacs that is trying to move from #svn to git with #ESR's help and having a difficult time of it?
โฒ @gnomon@mastodon.social: Recurring offer reminder: I'll help / mentor / teach / tutor / troubleshoot with anyone who wants to learn git for basic version control, collaboration, managing personal projects, or for a day job. I'll work to connect people with mentors other than me if they prefer - no need to explain why.
Same for bash, command line tools, and so on.
I want using & contributing to FS/OSS to be easier for way more people.
โฒ @starbreaker@mastodon.sdf.org: OK. Take a look at <sourcehut.org>.
@sir created this whole toolkit that supports both #git and #mercurial and provides most of the same functionality as services like Github, Gitlab, Gitea, etc. WITHOUT USING JAVASCRIPT.
You want public repositories? Sourcehut has it. Continuous integration? Wikis? Mailing lists? Patch submission by email? Gist/Pastebin? It's all there.
There's a hosted version at <sr.ht>, and you can self-host instead if you want.