My understanding of #Mercurial is that it is very comparable with #Git feature-wise. I only use Git because I discovered it first. It just so happens that it seems to have become the de-facto standard version control system these days.
For those who use Mercurial instead: why? Does it offer something that Git does not, or is it simply personal preference/familiarity?
I have a permanent branch that's never going to be merged into main. Is there any way to get GitHub to stop asking me if I want to merge it whenever I push new commits to it? I want this to go away for specific branches (I'll also accept it going away for all branches, because I mostly don't care about this).
🔴 Today on #SystemCrafters Live, we'll attempt to use Guix to self-host our own Git "forge" using Forgejo!
We'll package the Forgejo binary and create a Guix service so that it can be hosted in a container. We'll also see if we can wire up Laminar to launch CI builds when you push to repositories!
Okay. I really wanted to love #nbhttps://xwmx.github.io/nb/ for personal knowledge management. While most of its design choices (especially: #Git, #Markdown & #CLI) are exactly what I’m looking for, its todo management features are severely lacking:
• no arbitrary nesting of tasks (only top-level “todos” with a single sublevel of ”tasks”), no dependencies
• due dates are attached to todos, not tasks, can’t be queried(!) or repeat
• priorities, contexts etc. would need to be modeled via hashtags
I’ve gone from using the git command-line exclusively to almost exclusively using Sublime Merge.
I basically just keep it open on its own monitor as a real-time dashboard of all my changes. That, and the ease with which you can stage hunks and lines, has improved the quality of my commits and also gives me greater peace of mind.
(Downside: it’s a commercial app and Linux support exists but isn’t first class. e.g., doesn’t automatically respond to light/dark mode changes.)
What Github alternative are people using now? I've used many others for work projects, but never for personal, but I'd like to migrate out of Github at some point.
Is it weird that I feel completely comfortable with #git ?
I noticed that most of the folks #programming I run into are ill at ease when they interact with their repo.
The resources available tend to either
explain how (all of) git works.
Or
provide a few stanzas of incantations to accompany the ritual sacrifice.
I wonder if there's an audience for a "git therapist"?
"Do you think your struggles with merge conflicts may be rooted in early experience with svn ?...."
#git basierter Workflow für den #Betriebsrat. Ein Seminar. (warum nicht? mit Forgejo oder Gitlab hat man schon fast ein komplettes Ticketsystem und Dokumentenmanagement mit Versionsverwaltung ;)
Yay, #GitHub updated their docs to recommend the ~/.config/git/ignore for #Git’s global ignore file over ~/.gitignore_global. Using ~/.config is a standard, avoids cluttering your home directory, and requires no extra configuration.
Looks like a power outage during a bup backup killed the #Git repo it targeted and none of the rescue methods I’ve found have worked. Guess it’s time to switch to duplicity. 🤷
> Fixed a possible crash during the trophy cutscene that could happen if the stadium did not have a scheduled match and was not associated with an owning club.
#git pro-tip: register your SSH public key with your software forge (sourcehut, github, gitlab, etc.) and push/pull repos via SSH. Then use that same SSH key to sign your commits locally! Bonus points for deriving your SSH key from a FIDO/U2F hardware authenticator for extra security: https://wiki.archlinux.org/title/SSH_keys#FIDO/U2F
This introduction to Git aims to "reveal a bit of the simplicity underlying it". I'm not sure Git is as simple as it is to the author, but this work does help understand a little bit more on the tool and amek it feel less confusing:
🕺 From #Python 3.13, virtual environments created by venv will come with a #Git ignore file, thanks to @brettcannon ’s PR merged yesterday. There’ll be no need to add .venv (or whatever) to your .gitignore file then..
There was a time when I thought that #Git's commit ID being a Merkle tree style hash over all the content, including metadata, was a good thing. You change one byte anywhere in the history, Git notices instantly¹.
But I'm not so sure about this anymore. Names change. Email addresses change.
Should removing my previous name, that's now causing me pain, from the internet really break the integrity of my project?
¹ Actually, it doesn't. Not instantly. Re-hashing all of the history is expensive.
Hey Git experts, I'm thinking about moving to #Codeberg because I know Microsoft will scrape and steal everything on Github in the name of AI, if not soon, then eventually, and my question is, when I push and commit changes, how can I be sure it pushes to Codeberg and not Github, since I do have Github CLI installed, or does it push to where I pulled the repo from automatically? #Git
I know, Git is a mess. But, since we're stuck with it, we may as well try to learn how it works with resources like this, which aims to lead to some form of Git enlightenment.