canpolat

Git Rev News Edition 135 (May 31st, 2026)

15d 6h ago in git@programming.dev from git.github.io

Git Rev News Edition 134 (April 30th, 2026)

1mon 16d ago in git@programming.dev from git.github.io

Highlights from Git 2.54

1mon 27d ago in git@programming.dev from github.blog

How to build a git diff driver

2mon 6d ago in git@programming.dev from www.jvt.me

The Git Commands I Run Before Reading Any Code

2mon 10d ago in git@programming.dev from piechowski.io

Git Rev News Edition 133 (March 31st, 2026)

2mon 16d ago in git@programming.dev from git.github.io

Using Git with coding agents - Agentic Engineering Patterns

2mon 27d ago in git@programming.dev from simonwillison.net

git push? Do your pushups first

3mon 9d ago in git@programming.dev from git-push.app

I take full responsibility for this. I thought this was a parody. I didn't think anybody in their right mind would actually use this. In my defense their page contains of fake product reviews. Anyway... It's probably best to remove this, I'm perhaps mistaken. Thanks for the warning.

Git Rev News Edition 132 (February 28th, 2026)

3mon 16d ago in git@programming.dev from git.github.io

deff: interactive, side-by-side file review for git diffs

3mon 21d ago in git@programming.dev from github.com

How to Save Multiple Drafts in Git: A Guide to Using Stash

4mon 7d ago in git@programming.dev from www.freecodecamp.org

I would stay away from YAML (almost at all costs).

Branching strategy for a text based project

1y 3mon ago in git@programming.dev

For us to be able to help you, I think you need to give us some more details about the organization of your work. If each chapter is a separate text file, then you don't really need to do any branching at all (assuming people will only make changes on their own files and not touch others' work). If it is a single text file, branching (or anything else, to be honest) will not help much.

I assume chapters will have their separate files. As long as you can control who touches which file, everybody can work on the same branch (also referred to as "trunk based"). But if you fear that people may interfere with each other's work (willingly or by accident), then it makes sense to create a branch per chapter to keep contributors at a distance from each other. But working on a single repository requires some sort of an agreement on the workflow.

A second edition of clean code is being written

1y 10mon ago in books@programming.dev from programming.dev

This is an acknowledgement from Uncle Bob that the book didn't stand the test of time. We won't know before the new edition is out, but I suspect those pointless refactorings will not be in it any longer.

I keep getting logged out today. Is it just me?

1y 10mon ago in meta@programming.dev

This problem is now solved for me. I didn't do anything. Either a Firefox (current version 137.0.2 on mobile) or a Lemmy update (current version BE: 0.19.11) seems to have solved it.

I have the same problem on mobile Firefox on Android. I'm using the default frontend as well. This was not happening a week ago (or maybe 10 days). Started recently.

What are some good name suggestions for the rebranding of OpenSuse?

1y 10mon ago in linux@programming.dev from lists.opensuse.org

Don't they already have the names Leap and Tumbleweed? Changing the name to Leap would make sense since it's the name of the "official LTS" version. At this point it sounds like "openSUSE" is the name of the project and not the distro. But I haven't been following them closely, so perhaps I'm wrong.

Git isn't working when i clone, fetch, or push

2y 19d ago in git@programming.dev

Not sure but that sounds like you have a problem with your Git installation (or a dependency of Git). Maybe a reinstallation can solve that.

How Git Works (zine by Julia Evans)

2y 26d ago in git@programming.dev from wizardzines.com

I understand the "why would I pay for this" reaction. I think crowdsourcing is a better approach for these kinds of content. Once you reach certain level of financial commitment from the crowd, you can give away the PDF and sell the print copy.

git branches are just homeomorphic endofunctors mapping submanifolds of a Hilbert space

Yeah, once you realize that everything falls into place.