jcayzac (@jcayzac@mastodon.social)
I pushed my first #git repo to the #radicle network, today. UX-wise, it's very nice. Not in the way at all. `rad init` and it's just another remote to push to. Pretty cool!
Show Original Post
notes (@notes@852260996.91268476.xyz)
Is it too dumb of an idea to make a git repository of your $HOME? It sounds like a good way to automate backups and check in case you overwrite a file, but I feel that I’m missing something, otherwise everybody would be doing it already. #git #selfhosted #dumbquestion
Show Original Post
Liquidator (@Liquidator@gamerstavern.online)
I damn love Godot and its community. Installed Gitea on my NAS and now I was searching for visual GIT application that will work on my Fedora. Found out I can just use plugin inside Godot. Simple, efficient, easy. Works perfectly.
Plugins GitHub: https://github.com/godotengine/godot-git-plugin/
#godot #git #gitea #fedora #indiedev
Show Original Post
events (@events@mobilizon.fr)
[non-mixité] A-t-on encore besoin d'Agilité en 2026 ?
12 mars 2026, 18:30:00 CET - GMT+1 - Zenika, 59110, La Madeleinehttps://mobilizon.fr/events/d0019cef-4dd3-4e30-aeb5-a0e9c4a458dc
Show Original Post
Bluedonkey (@Bluedonkey@mastodon.social)
RE: https://mas.to/@zekjur/116022397626943871
Never ceases to amaze me how bad #git is. Just far too many ways to create accidental errors (and, from what I recall of interviews with its creator, that was intentional).
Show Original Post
nathansmith (@nathansmith@hachyderm.io)
🌭 Analogy for the yolo posts I see — citing an industry expert or veteran, where those cherry-picking quotes are typically neither — about why nobody needs to read or understand AI-generated code anymore.
– Eating corndogs at the state fair.
– Honestly, you know it is bad for you.
– But if you do not think too much, you can convince yourself that maybe *this* unknown brand of mixed meat is actually healthy.
– As long as you never thoroughly check, you need not validate any correct (or likely, incorrect) assumptions.
🤷 Ignorance is bliss. And lately, I have been encountering *lot* more willfully blissful people. Even folks who should probably know better.
Personally, I tend to think of AI as info during the Cold War.
> "Trust but verify."
https://en.wikipedia.org/wiki/Trust,_but_verify
Show Original Post
danbelascorogers (@danbelascorogers@mastodon.art)
Finally moving some of my git projects on to Codeberg (thanks @celesteh) has made me get all 'cody' again. https://Codeberg.org/belasco
#codeberg #git #python #pdm
Show Original Post
calisti (@calisti@chaos.social)
@jugglerchris @jamie @fasterthanlime Another reason for rebase-only workflows is that most #git forges only run CI on the source branch as it is, but not on the target main branch as if the source branch was already merged.
Thus, you can easily end up with a changeset that succeeds in CI but fails once combined with other changes on target branch. You’ll only notice after merge.
Always enforce rebase workflows, and always enforce the source branch branching off the tip of the target branch.
Show Original Post
calisti (@calisti@chaos.social)
@jugglerchris @jamie @fasterthanlime The security liability is that you can hide code changes in merge conflict diffs which do not show up in the history diff views without providing extra parameters.
Here’s a neat demonstration: https://tavianator.com/2025/sneaky.html
Show Original Post
dazo (@dazo@infosec.exchange)
😱 😱 😱 😱 😱 😱 😱 😱 😱 😱
What are you going to break now!?!?
#atlassian #bitbucket #programming #sourcecode #vcs #git
Show Original Post
heptapod (@heptapod@fosstodon.org)
#heptapod 18.8.0rc1 released, featuring #gitlab 18.8.3
Docker: https://hub.docker.com/r/heptapod/heptapod/tags?name=18.8.0rc1
Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.8.0rc1/HEPTAPOD_CHANGELOG.md #git #mercurial
Show Original Post
Grollicus (@Grollicus@infosec.exchange)
Inline-Protokoll stolpert über verkackte Message Boundaries, news at 11. Ist ja nicht so als hätten wir bei quasi jedem inline Protokoll schon solche Schwachstellen gesehen (http request smuggling, dito an smtp „gateways“, dito in alten irc servern offhand)
Jetzt also auch #git emails.
Bin gespannt wie sich das entwickelt. Aber generell vmtl. interessant zu schauen ob man bei diversen Tools aus commit message / MR-Kommentar code am Review vorbei schmuggeln kann.
Show Original Post