emaechler (@emaechler@masto.maechler.cloud)
alle #push zu #git #forgejo werden wegen auth fehler abgelehnt.... ich hab es mit token und ohne versucht mit pw und ohne.... gopf - sicher irgend ein dummer kleiner fehler der mich in den wahnsinn treibt...
Show Original Post
emaechler (@emaechler@masto.maechler.cloud)
ich bin echt zu blöd für dieses #git ... langsam nervts mich
Show Original Post
j4ck (@j4ck@iosdev.space)
Teaching a friend git, recapped all the steps up-to merging a PR:
Jack: "Feel good?"
Friend: "Well, I don't feel good."
😆 #git
Show Original Post
sanjay_ankur (@sanjay_ankur@fosstodon.org)
Zaphod, #Python wrapper around #LaTeXdiff, is now on #PyPi as zaphodtex
`pip install zaphodtex`
https://ankursinha.in/2025/09/19/zaphod-is-now-on-pypi-as-zaphodtex.html
#LaTeX #Git #Zaphod #AcademicChatter
Show Original Post
fergus (@fergus@mastodon.cosroe.com)
I've now submitted my #phd #thesis which means I've finally settled on a title 🎉
General relativistic effects in black hole X-ray coronal models
I posted previously about my progress indicators. I'll be writing a #blog post about them soon and how I used #git trailers and #python scripts, but here's what the final word count plot looked like. The three day gap was when we had some conferences going on here in Bristol and I had to stop writing to be on the LOC, and prepare and present a talk.
Show Original Post
david_guillot (@david_guillot@social.tchncs.de)
6 Months ago, thanks to @lobsters , I read this: https://mirawelner.com/posts/checkout.html
Haven't used `git checkout` once since.
Show Original Post
devdigest (@devdigest@mastodon.social)
⚡️ VS Code SQL Extension Adds Microsoft Fabric Preview Features
🏷️ #devdigest #dotnet #net #microsoft #ide #vscode #visualstudio #git #github
https://devdigest.today/goto/4883
Show Original Post
frontenddogma (@frontenddogma@mas.to)
Learning Web Development: Version Control via Git and GitHub, by @rauschma:
https://2ality.com/2025/09/git-github.html
#versioncontrol #git #github #commandline
Show Original Post
item (@item@zotum.net)
@Eduardo Mercovich (él)
This is a lot of thanks for a modicum of effort, during which I improved my elisp — and it does very little to address the state of the world, alas!
Can I suggest you put your thesis under version control as soon as you can, if it's not already?
The day you realise your sweeping edits were the wrong idea it will save your hide, and it's often useful less dramatically on other occasions.
For a single document being worked on by a single person, you really need very little knowledge of git. Just three very simple things: how to set it up, how to store changes, and how to retrieve a previous version. You don't even really need to know how to retrieve to start with — you could happily leave this until later, even deferring this until you really need it. You could even in a pinch get someone else to do it. Whereas they can't help you if you don't have previous versions in a repository!
Setting things up
- navigate to the directory/folder your thesis is in, and
git init --initial-branch main
git add thesis.org'git init' sets up an empty repository. you don't need the --initial-branch argument but if you don't git will call it 'master' which some find offensive. As you may be making this public you may as well avoid this controversy.
(You do not need to worry about branching at all - I can't see why you'd want to branch your thesis. But there's always at least one branch and things like codeberg will display its name.)
'git add' is perhaps a little misleading. The repository is still empty at this point, you've just told git to track the file 'thesis.org' and store changes to it when you commit - which is the next step.
Storing changes
git commit -m "a message describing very briefly what changed"This stores all changes to the files git is tracking to the repository. After the first commit the repository will now have a copy of thesis.org in it, in the state it was when you committed it.
'-m' is for 'message' naturally.
"initial commit" is a traditional first commit message. Other examples might be "fixed references in chapter 3", "incorporated jamie's code" etc.
I recommend committing pretty frequently - maybe every day!
And that's all you need to know!
(I'm assuming you have git installed already. Let me know if you need help with that.
Also, I know you want to use magit but I've barely ever used it, and for these very simple use cases I think it's worth learning to use command line git. It means you can understand what others are talking about, and also cope if magit isn't available).
@Eduardo Mercovich (él) #tem25 #git #versioncontrol
Show Original Post
mjambon (@mjambon@mastodon.social)
I wrote a guide where I give a workflow for using Graphite's stacked PRs: https://dev.to/mjambon/a-guide-to-using-graphites-stacked-prs-for-github-users-5c47
Graphite augments Git and GitHub (or GitLab), facilitating the creation, review, and revision of series of small pull requests.
#git #programming #github #graphite
Show Original Post
hn50 (@hn50@social.lansky.name)
OneDev – Self-hosted Git server with CI/CD, Kanban, and packages
Link: https://onedev.io/
Discussion: https://news.ycombinator.com/item?id=45291590
Show Original Post