„Vorwärts immer, rückwärts nimmer!“
git pull --ff-only
„Vorwärts immer, rückwärts nimmer!“
git pull --ff-only
Great #git tweaks Micah's Secret Blog https://micahkepe.com/blog/gitconfig/
TIL: should I use single or double quotes in git commit messages?
both works fine, but go for the single quotes; double quotes might trigger "command substitution" on unix-like systems
for example:
```bash
$ echo "`ls`"
./docs/
./node_modules/
./package-lock.json
./package.json
./pages/
./README.md
```
I wish that game dev peeps would see that Git for large graphics files is a real problem.
No, LFS does not help you.
Every change to your 2gb blender file is an ENTIRELY NEW FILE.
Am I wrong?
It seems we badly need a git for design/binary files that does not multiply megabytes.
Cours d'introduction à #Git et #Gitlab pour des doctorant.e.s (3h) https://zenodo.org/records/18889874
Pünktlich zum Wochenende gibt es eine neue Folge. Beide hatten eine ruhige Woche. Dennoch gibt es Neues zu berichten.
Hört einfach mal rein.
👉 https://ready-for-review.dev/2026/03/06/rfr094-preiserhohungen-und-katzen/
You just reorganized your project and renamed several files. When you check your history, Git cleverly shows that the files were "renamed" rather than deleted and recreated.
How does Git actually record this rename action under the hood? Vote below👇
Check out the right answer here 👉 https://www.youtube.com/post/UgkxmMT_wtEzWjcA7ekoo5GLkI2N32yJzHPF
#SmartGit #git #SoftwareEngineering #WebDevelopment #CodingLife
Thank you @stefanzweifel (& contributors) for git-auto-commit-action.
Yesterday I learned that one can sign #git commits with their ssh-key. I prefer that so much over signing with a gpg-key tbh. Even my mobile git-client WorkingCopy can do it.
Is there a way in #git to prevent a file being added to the repo, but without listing it in `.gitignore`?
Currently I'm just adding all files each commit except one particular one, but it's tedious and I have to remember not to just do `git add .`
✍️ I usually write about HTML, CSS and JS. Doing a bit about git feels alien to me. Primarily I put it out there to attract crowd wisdom.
I have now moved my biggest open source project (my website for sports rankings) from #GitHub to @Codeberg 🇩🇪. I encourage other Europeans to also promote the adoption of European tech 🙂
I do work with #git branches a lot, switching forth and back between them, rebasing and executing commands on many source code states (e.g. git rebase --exec …, or git bisect).
The #RustLang survey shows that slow compilation and high disk space usage are an important concern for users of the language.
When performing the workflows mentioned above, they hit especially hard and have a high cost. I really hope these are a top priority in the development of Rust.
@CenterforOpenScience Any chance the #OSF will start supporting #Codeberg as an add-on for projects? I imagine the Venn diagram of people into #openscience and people wanting to get off #Github has a lot of crossover.
dotGit — minimal dotfiles manager built on a bare git repo + shell aliases.
What I use most: `.gg PATH` greps all tracked dotfiles and takes you to the line. `.ge zshrc` fuzzy-finds a filename with preview and opens in $EDITOR.
No symlinks or extra tooling. Files stay exactly where they are.
🔗 https://code.opennomad.com/opennomad/dotGit
(mirrors: https://codeberg.org/opennomad/dotGit · https://github.com/opennomad/dotGit)
#linux #dotfiles #bash #git #selfhosted #opensource #commandline
Because we rely heavily on cloud to host our #code, it’s easy to think of them as the absolute source of truth.
But structurally? Git doesn't care about the cloud ☁️🚫
Every time you clone a #Git repo, you are downloading a full-fledged, 100% complete backup of the entire project history.
#SmartGit embraces this local-first power, giving you full control over your repo whether you have a Wi-Fi or not.
Have you ever had to keep working entirely offline during a server outage? 🌍💻
Some time ago, I toyed with the "crazy" idea the the ideal name for the primary branch in a #Git repo wasn't _master_, _main_, or _trunk_, but rather _/_ — becuase then you could treat it as the root of a directory tree, with branches named as if they were subdirectories under the branch they were branched from.
I messed around a bit with this idea, and it turns out that Git disallows _/_ as a branch name (because branch names are stored as filesystem paths under `.git/refs/heads`).
Now I'm considering something that unironically doesn't sound crazy at all: name the primary branch _after the short name of the project_, and then name branches according to the tree structure mentioned above. That would get you such branches as:
```
example-proj (primary branch tracking prod)
example-proj/staging (branch tracking staging env)
example-proj/develop (main development branch)
example-proj/develop/<feature> (feature branch)
```
It would look weird at first and require a tiny bit more typing (which can be alleviated with autocomplete), but it also feels _right_ in a certain way.
I will need to play around with this more.
Git in Postgres
"Instead of using git as a database, what if you used a database as a git?"
Each #OpenBSD virtual machine hosting #Git repositories on the #GameOfTrees Hub is configured by editing the gotsys.conf configuration file.
We run a live demo which shows configuration examples to help new users with getting started: https://demo.gothub.org/
Oh! I forgot to share the results of #Emacs abstinence experimemt. In these two (or three, I lost count) weeks, I
• Moved all text editing (including my #CommonLisp library maintenance and blog writing) to #ed(1)
• Used console #Git for most workflows, and ed(1) for interactive rebase (I’ve grown to like it)
• Only used Emacs for emails and minor Magit
• Changed three terminals (st -> URxvt -> XFCE Terminal)
• Moved many if my workflows to the browser, because that’s the most featureful platform and ecosystem after Emacs
Overall, I’m relatively confident I can live without Emacs. But such life would be slow, unresponsive, and ineffective. So I’m back to Emacs, because I value my time and sanity. As should you.
If you ever used older version control systems like SVN, you were probably taught to think in "diffs".
But Git doesn't think like that 📸 It operates like a mini file system:
✅ When you commit, #Git takes a snapshot of what your files at that moment
✅ If a file didn't change, Git creates a pointer to the previous identical file.
#SmartGit visualizes these snapshots so you can seamlessly jump between different moments in your project's history without the mental gymnastics.
🎮 From #AI-generated music to 3 native #Linux #games and a #Git workshop, planet.o.o gives tons of insights into #OpenSource. Installing #openSUSE on the HP Z2 Mini, no problem. All this and more in this week’s roundup! https://news.opensuse.org/2026/02/26/planet-roundup/
Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
No sé si estoy preparado para resolver conflictos en #git
buf, me pierdo...
No sé si alguien está preparado para eso!! jejeje