What is stopping you from migrating away from #GitHub?
#Programming #Programmers #Coding #Coders #SoftwareDevelopment #WebDevelopment #AppDevelopment #Developer #Developers #WebDev #AppDev #AiDevelopers #AiDev #Git #VersionControl
I've just figured out, that i can use #GitHub without using the #Git command line tool! 👍
That makes sharing #code so much easier!
My 1st commit 👉 a #ZFS replication routine for my #Steam #gaming partition/pool. It's better than #rsync, because ZFS send&receive just DOES what its told, instead of noping out processing those #Proton files.
Here's my #Linux #Bash helper #script #repo: https://github.com/PurryPlatypus/bashrc.d
https://jordankasper.com/git/#/ - A cool deep dive into #git commands. Great presentation at #ConFoo Jordan Kasper.
Entwicklungsplattform: GitLab 18.10 führt Anmeldung per Passkey ein
Das Release ermöglicht die passwortlose Anmeldung mit Passkeys und erkennt falsch positive SAST-Vulnerabilities mithilfe der GitLab Duo Agent Platform.
#ContinuousIntegration #Entwicklungsumgebung #Git #IT #Passkey #Versionskontrolle #news
Heute frisch gebaut:
Lore: Git Commit Messages als strukturiertes Wissensprotokoll für KI‑Coding‑Agenten
https://agentenlog.de/posts/2026-03-20-lore-git-commit-messages-structured-knowledge-protocol-ai-coding-agents
#Agentenlog #kicodingagenten #git #decisionshadow
Your eyes are burning at 2 AM? 👁️🌙
If you’re squinting to see a merge indicator or struggling with inconsistent tab borders, you aren't coding—you're fighting your tools..
In the latest SmartGit's preview, we stopped fighting and started refining 🚀. We didn't just turn the background black:
✅ We reworked the toolbar icons,
✅ improved contrast,
✅ and deepened the theme to reduce eye strain during those long-haul sprints.
#UX #SoftwareEngineering #SmartGit #DevTools #DarkMode #Git #GitGUI

@tiotasram Read this article to understand why rebasing is the best of the three strategies to integrate a pull request.
https://www.sandofsky.com/git-workflow/
There's only two reasons why developers dislike/misunderstand this merge strategy (and one reason that prevents them from choosing this strategy):
- They are too lazy or incapable of creating a clean commit history. Due to their unwillingness/inability to create good atomic commits, they would litter the default branch with "WIP" commits if they followed this merge strategy.
- They like to see visually when a branch branched off of the default branch and merged back into it. This is an anti-pattern and would better be done with git tags.
- The single valid reason to not choose this strategy, in my opinion, is because your command to auto-delete merged branches no longer works. Rebasing changes the hashes of commits and thus git is no longer able to detect that a branch has been merged. This means you either need to delete your branches manually or end up over time with a long list of obsolete branches.
Linux DevOps eBook Bundle by Bobby Iliev is the featured bundle on Leanpub!
Link: https://leanpub.com/b/linux-devops-ebook-bundle
#Databases #Mysql #Postgresql #ComputerProgramming #Devops #CloudComputing #Git #VersionControl #ComputerSecurity #ProgrammingCookbooks #SoftwareEngineering #Terraform
I remain convinced that the #Git CLI is a terrible UX and an especially bad fit for AI agents. Evidence:
```
GIT_SEQUENCE_EDITOR="python3 -c \"import sys; p=sys.argv[1]; c=open(p).read(); open(p,'w').write(c.replace('pick 29507ade4d6', 'edit 29507ade4d6'))\"" \
git rebase -i 29507ade4d6^
```
I only asked it to take some local changes, break them up, and amend them to some existing individual commits and it is thrashing *wildly* but I'm scared to abort or it'll leave me in a potentially worse state.
I'm been playing with #Jiujitsu on the side, I wonder if that might work better?
@memoriesin8bit I find this "How Git Works" #zine from @b0rk (Wizard Zines) to be extremely helpful to have around.
https://store.wizardzines.com/products/how-git-works
#Git is extremely powerful and extremely hard to learn beyond the basics 😅
Funny. So something in my settings is blocking me now from logging into #gitlab
I ruled out extensions and network, so it must be some setting. But it never did this before, and I haven't changed anything recently. I can access with some workaround, but it's bothersome
Why start blocking me? For having privacy-respecting settings? Is it a false positive, or a begin of decline?
It annoying to say the least. Wonder if @Codeberg minds if my only #git usage is my recommendation list and not code?

Why did it take me almost two decades to learn about the git add -p option? That would have been very useful on many occasions.
#git