2026-01-04 09:31:23
You already have a #git server
https://maurycyz.com/misc/easy_git/
#GitPages now implements an audit system that allows on-line, background processing of uploaded content to e.g. scan it for viruses, phishing, and other abusive material
I consider this table stakes for any service with open registration, so now I can finally say that git-pages is _almost_ done (it needs a GC and a few minor fixes to other functions)
{piggyback} makes it easier to attach large files (e.g. input data) to code in github repos: #rstats
Does anyone have experience with #gitSubRepo? It seems to be a more ergonomic version of #gitSubTree that e.g. remembers remote urls to spare you lengthy syncing commands.
Git merge flatten is a mistake and a skill issue from those with bad git history visualisers.
#git
TIL: gitignore.io ist unmaintained. Die Firma, die das aufgekauft(?) hat, hat große Teile der Quellcodes auf github gelöscht und die Templates werden wohl nicht mehr Aktualisiert. Gibt wohl Versuche ne Alternative zu schaffen, z.B. donotcommit.com, sehen bisher aber auch eher unfertig aus :/
#git #github
Monorepo vs Multi-repo vs #Git submodule vs Git Subtree: A Complete Guide for Developers
https://levelup.gitcon…
If you're going to police git history messages of a feature branch I'm out.
#opensource #git
I'm using #git subtree for the first time in a real setting. It feels nicer than git submodules, because you can just commit and everything downstream is included. You can then push the individual subtrees later and it'll pick only the commits that actually touched their directories. `git log` gets a bit crowded though with duplicate commits (from parent and subtree repos). And there's no …
For hosting our internal source code repositories, we're using #gitea. There are a bunch of other options and all of them seem to mimic github's look and feel. Gitea was the one I found out about first some years ago and it stuck. It has an issue tracker and works well for doing pull requests and reviewing them online.
There's a commercial cloud hosting offer and an enterprise opt…
I frequently create a new #git :git: repo and it always bothers me to manually create .gitignore file myself.
Today I automated this with the following lines in my .bashrc
# define the content in an env var
GIT_IGNR_CNTNT=$(cat <<-EOF
*.log
tmp_*
# put other patterns here
EOF
)
# function to write env var to file
git_ignore_creation(){…
I it bugs me a lot when I see HTML pop up in #git commit messages. I think it's an unfortunate combo of 4 things leading to it: People don't trust their forges for archival (which is good, but then please just use Reviewed-on footers with URIs and use web archival tools), MarkDown being the mess it is allowing HTML as fallback, forges taking in their mdwn into commits (worse: squashes), and bot…
I'm looking for "alpha testers" for an alternative forge ( based on #Forgejo )
#floss projects, likely paid for private projects (although we are providing the service for free for a while, until we do an official launch).
Once/If we start having paid customers, we'll donate part of that income to the upstream Forgejo project.
This forge is 100% hosted in #Europe, and operated & maintained by a very small workers-owned #coop .
P.S.: Yep, we know about the great Codeberg :) .
#BetaTesting #Git
#TIL that #Gitolite can't handle repositories with different default branch names. As in, if you push a "main" branch into a "master" server, you get no HEAD 🤦. And you can only change that via SSH-ing to the server and modifying the underlying repository.
Apparently, you could also install a hook to automatically fix HEAD for you: #Gentoo #git