ingewikkeld (@ingewikkeld@phpc.social)
Beveilig je codebase! Onze Git-training leert je team hoe ze commits kunnen signen en verifiëren om de integriteit van je software te waarborgen. #Git #Security #SoftwareDevelopment
https://ingewikkeld-trainingen.nl/trainingen/geavanceerd-gebruik-van-git/
Show Original Post
sikorski (@sikorski@social.tchncs.de)
Sie können jederzeit mit der Portierung von Doom auf ein neues Gerät beginnen !
git clone https://github.com/id-Software/DOOM.git
or
gh repo clone id-Software/DOOM
https://github.com/id-Software/DOOM
#gamedev #code #source #doom #git #github #classic #game
Show Original Post
smartgit (@smartgit@techhub.social)
Now available: SmartGit 24.1.5 — incl. fixes for Azure DevOps, GitHub starred repos, GitLab tokens, plus official macOS 26 Tahoe support. Ready for testing: https://www.smartgit.dev/download
Show Original Post
farooqkz (@farooqkz@cr8r.gg)
I hate it. It ruined me...
So now there are two #MinetestCTF codebases. The original #CTF by rubenwardy was forked at one point, and #JMA was created.
Now me trying to contribute to both codebases... a real nightmare. I opened a PR on JMA first:
https://github.com/Minetest-JMA-group/jma-capturetheflag/pull/101
Then I thought let's do git format-patch and create some patches to apply to main CTF using git am but no. Heck no. The files have diverged. So applying a patch is not automatic and straightforward. alright alright I can take it. Let's apply the patches manually...
Once I did, I realized I had to change something. Updating the patches for JMA then for main CTF. Okay they should be fine now. I still can do it.
Now I realized the code needs a refactor because now there are 2 mods which depend on each other and this is not allowed.
Heck no!
I do wish developers of JMA and also developer of main CTF would come to a common ground. Otherwise, I cannot contribute to both codebases like this while they have diverged so much.
#softwaredevelopment #softwareengineering #luanti #gamedev #git #foss #opensource #free_software
Show Original Post
thomasmey (@thomasmey@social.tchncs.de)
Underrated episode: on code review
Oxide and Friends: On Code Review
Webseite der Episode: https://share.transistor.fm/s/9a011c9c
Mediendatei: https://media.transistor.fm/9a011c9c/0d514c3b.mp3
Show Original Post
dxzdb (@dxzdb@mastodon.social)
#xcode #git hell...
I started using Fork as a git tool - it's great! But I think I need to do any branching / switching inside Xcode rather than Fork because it seems like Fork can't see certain files. Maybe a setting somewhere. I'm sure it's PICNIC (Problem in Chair, Not in computer) 😏
Show Original Post
clonbg (@clonbg@masto.es)
Hacer que git no pida contraseña https://myblog.clonbg.es/hacer-que-git-no-pida-contrasena/ #Git #Seguridad https://clonbg.es
Show Original Post
timj (@timj@social.tchncs.de)
#DevLog: jj-fzf: Screencasts & E2E Tests! 🔍
🔧 Fixes & UX improvements
→ Fixed missing bookmark separators
→ New Oplog key bindings to stay on current operation
🎥 Pushed New Screencast Demos
→ Oplog undo/redo, inject commit, restore repo (attached)
→ Bookmark/tag editing, move, delete
→ Revset editing with live reload
→ Improved screencasting: key / description popups, improved reproducibility
🧪 E2E Screencast Tests
→ CI now runs screencasts and checks outcome
→ Asciinema screencasts are downloadable CI artifacts
→ New script render.sh to render screencasts to GIF/WebP/MP4
→ New test-screencasts target in Makefile.mk
https://github.com/tim-janik/jj-fzf
#Jujutsu #VCS #jjfzf #BuildInPublic #100DaysOfCode #Git #CLI #DevTools #OpenSource #ShellScript
Show Original Post
gatelinker (@gatelinker@fosstodon.org)
#Release days... I hate them. 😩
It's the time where bugs become visible that where postponed with a smile for months.
I can remember when a "release" was just copying one file to a #floppy disk and a handover to a friend.
Today we need masses of #git pull/merge/review/tag tasks followed by repackaging and uploading binaries, docs and test-reports for N+1 required platforms.
And all of our performance gains on build servers is eaten up by new bureaucracy.
But it works, somehow.
Show Original Post
Serpent7776 (@Serpent7776@mastodon.social)
A very professional way to per-commit benchmark the code. #git
git rebase --autostash --exec ./bench.sh start_commit
Show Original Post
edlinks (@edlinks@mastodon.social)
#Git: From Zero to First Commit - Developer Journey Begins. https://dev.to/swathi_macha/git-from-zero-to-first-commit-developer-journey-begins-170d
#programming #software #development
Show Original Post
cark (@cark@social.tchncs.de)
Today, we had a fire alarm going off at @tudresden when I was just working on a local 
repo.
This reminded me on the popular meme:
In case of fire 🔥
1. git commit
2. git push
3. leave building
I always had some mixed feelings about it. Thus, I wrote down whats wrong with this meme on several levels (technical and social):
https://cknoll.github.io/git-fire-en.html
Show Original Post