jcolomb (@jcolomb@nerdculture.de)
Hey, I am looking for a video that introduces Git and Forgejo (i.e. not Github) which has a permissive license.
if possible short ;)
Anyone knows of something?
#git #codeberg #training #oer #openscience
Show Original Post
benjohn (@benjohn@todon.nl)
Very tiny #git tip.
Git commit hashes are quite long, so many tools will shorten them.
I believe the “consensus” is to display a shorter **prefix** of the full hash, removing characters from its end.
As such, if you want to match commits by eye, you also should use a prefix. If using just a few characters to match, you should check from the start, not the end.
For some reason this always surprises me, so this is part of my attempt to remember this!
Show Original Post
me (@me@joshuastrobl.social)
I was today's year old when I learned about #git commit cleanup "scissors" mode. I had swapped to whitespace a long time ago so I could maintain use of # for headings of more in-depth commit descriptions, but always had to clean up the git commit generated text.
With scissors mode, anything below that line is cut, no manual cleanup needed!
https://git-scm.com/docs/git-commit#Documentation/git-commit.txt-scissors
Show Original Post
davidculley (@davidculley@hachyderm.io)
RE: https://hachyderm.io/@davidculley/116072772184382847
To all software developers or people using #git version control:
This video really helps with understanding git better if you're already comfortable with the basics.
Show Original Post
Rudolf (@Rudolf@mastodon.de)
Kennt ihr das: Ihr entwickelt an einen #Projekt und habt, wie ich z.B. gestern, wieder dutzende Zeilen #Quellcode in das #Git #Repo eingecheckt und gepusht, aber eigentlich das Gefühl ihr seit wieder an dem Tag mit dem Projekt nicht voran gekommen so wie geplant und habt keine Ahnung, wie ihr das Projekt voran treiben könnt. Außerdem seit ihr gerade vom Projekt ermüdet, da ihr zuletzt fast nur an diesen einen Projekt gearbeitet habt und wollt eigentlich zur Abwechslung mal was anderes machen. Allerdings die Deadline rückt immer näher und zeitlich ist das Projekt sowieso schon viel zu knapp kalkuliert.
An dem Punkt bin ich gerade, zumindest bei einem Projekt.
Vielleicht mal an alle anderen #Entwickler*innen da draußen die Frage:
Was tut ihr, um mit einer solchen Situation umzugehen und wieder #Motivation sowie geistige Anregungen für das Projekt zu finden?
Show Original Post
ppb1701 (@ppb1701@ppb.social)
Gitea, Smarter Monitoring, and the Syncthing Permissions Fight — Part 11 of Building a Bulletproof Home Server Series
Time to get some source control under my own control and fix a few issues.
#blog #homeserver #nixos #gitea #git #syncthing #selfhosted
Show Original Post
dxzdb (@dxzdb@mastodon.social)
Apparently I somehow messed up a git remote in an old project (years ago) such that when I pushed a new project to GitHub it started showing new project commits in the old project remote.
The fix? "git remote rm origin" or in Xcode under "Remotes" hit delete.
#git #xcode
Show Original Post
jimgar (@jimgar@hachyderm.io)
For the first time this past week, I had to turn a regular git repo into a bare git repo.
Bare repos aren't something I've ever had to think about, and I guess a lot of people don't, because almost everyone uses third party services with git: GitHub, Codeberg, etc.
A non-bare repo is for when you're working alone. It's the default when you do `git init`, or `git clone`. You get a `.git` folder with all of the git tracking info. If cloning, git will also construct copies of all the files you'd expect to see, like the readme, code, configs, etc.
You can't have two or more people working in one of these normal repos, like on a shared file system, because if Person 1 checks out a branch called `feature_a`, that means everyone else now also has to work on that branch. I'd expect it to cause all sorts of other problems, too, but I'm not 100% sure what they would be. The point is, you have a non-bare/working repo, and it's just for you.
A bare repo is for when you want to COLLABORATE. When you make a repo on GitHub or whatever, that's a bare repo. You and your collaborators each clone a working copy with `git clone`. If you don't have GitHub/whatever, but rather have a shared server or something like that, then you can start a bare repo in an accessible directory with `git init --bare`. Then, collaborators `git clone` from there to get working copies, and push/pull.
My team work in an air-gapped Trusted Research Environment, with only vanilla git available. Last week, the DataOps team cleared one of my GitHub repos into the TRE, and I had to convert it to a bare repo so my team can collaborate. I could have used `git clone --bare` to convert it. But to understand the difference between bare and non-bare better, I did it manually.
A bare repo is essentially just the contents of `.git`, with no other working files.
So this is all you have to do to convert:
1. Make a new directory wherever your bare repo is going to live
2. Copy the CONTENTS out of the working repo's `.git` directory, into the new directory
3. In the new directory edit `config`, changing `bare = false` to `bare = true`.
Now you can `git clone` that repo and *even though there's no working files in the bare repo* they will appear in your cloned repo.
Show Original Post
emanuelegori (@emanuelegori@mastodon.uno)
#Dockhand: una Web UI moderna che unisce log live, monitoraggio aggiornamenti e deploy automatici da #Git in un’unica dashboard. Scopri come installarlo su #VPS o #homelab
Show Original Post
noamross (@noamross@ecoevo.social)
I've long been a fan of Dolt, one of the better solutions of "git for data" that I've seen. Super excited for this latest feature they have, of storing the dolt database directly in a git repository: https://www.dolthub.com/blog/2026-02-13-announcing-git-remote-support-in-dolt/
Show Original Post
objects (@objects@pleroma.interhacker.space)
$ git git commit -m 'hexablob + openbox -> boxed_blob' contexte.inc essai.pov gadgets.inc
git: 'git' is not a git command. See 'git --help'.
$
J'crois que c'est clair, #git ne se connait pas lui même...
Show Original Post
simsus (@simsus@social.tchncs.de)
#GitHub führt Maßnahmen gegen KI-Slop ein – ohne das Problem klar zu benennen | heise online https://www.heise.de/news/GitHub-fuehrt-Massnahmen-gegen-KI-Slop-ein-ohne-das-Problem-klar-zu-benennen-11176641.html #ArtificialIntelligence #AI #AIslop #git 
Show Original Post