pjacock (@pjacock@fediscience.org)
Should have double checked before leaving the house, but I didn't run 'git push' from the desktop so now I can't resume that line of work from my laptop 😢 #git #GitPush
Show Original Post
TheTomas (@TheTomas@social.toot9.de)
Die eigene #Forgejo Instanz anpassen? Wenn das Grundkonzept bekannt ist, geht es ganz einfach:
https://blog.jakobs.systems/blog/20251117-forgejo-customization/
#git #opensource #development #gitops
Show Original Post
xolatgames (@xolatgames@mastodon.gamedev.place)
Oops! 😅 Sorry about this, but I already have fix the issue where you can't picks up keys 🗝️
👉 https://codeberg.org/xolatgames/Vasya-go-to-home/releases/tag/v0.2.1
#rust #rustlang #cargo #opensource #git #codeberg #inkscape #2d #maze #adventure #ActionAdventure #game #games #gamedev #development #devlog #macroquad #tiled #TiledMapEditor #devlogs #appimage
Show Original Post
nurkiewicz (@nurkiewicz@fosstodon.org)
If #git made sounds, I could listen to `git rebase` reapplying several commits cleanly, as if it was the best #ASMR.
Show Original Post
rnb (@rnb@framapiaf.org)
Quelle stratégie(s) adoptée(s) pour versionner un projet plein d'images avec #git ?
On peut utiliser git-lfs <https://git-lfs.com/> qui évite que l'historique ne devienne un trou noir.
Si l'historique des images n'est pas utile, on peut les exclure dans .gitignore.
On peut en versionner certaines (le travail sur des fichier .xcf) et pas d'autres (les exports en .png).
D'autres pistes ?
Enfin, le #versionning n'est pas une sauvegarde ! Il ne dispense pas d'en faire 😃️
Show Original Post
opensuse (@opensuse@fosstodon.org)
Want your #desktop setup to follow #GitOps principles? Check out this #oSC25 talk on running your #WindowManager & apps in non-root containers, all from declarative #configs in #Git. Secure, #portable, version-controlled. #Linux #Containers #openSUSE https://youtu.be/KBWfGMUBGgI?si=i1KtKCnSnmbs3Fji
Show Original Post
lemeteore (@lemeteore@mastodon.social)
And I'm discovering, other people does #git diff using a #pager named #delta 🤔 
I feel really old sometimes 😅
Show Original Post
forge (@forge@gts.gitroot.dev)
Tests, tests, tests!
GitRoot has unit tests, of course, but it also has a lot of end-to-end (e2e) tests.
It's really easy to write e2e tests in GitRoot because everything is stored in files. You have Git? You can write tests! As you can see at the link, the tests are just #Bash scripts using `git`, `echo`, and `grep` to assert.
Our main runtest.sh tests:
- 4 repositories
- 2 users
- 4 plugins
- 42 commits / 41 pushes
...all in ~40 seconds!
https://gitroot.dev/worktree/app/testsuite/
#Testing #E2E #Bash #git
Show Original Post
reddit_tech_vn_bot (@reddit_tech_vn_bot@mastodon.maobui.com)
Vizier là công cụ giúp cá nhân hóa quy trình phát triển Git với Codex:
- **ask**: Gửi yêu cầu phát triển
- **draft**: Tạo nhánh công việc cụ thể
- **approve**: Thực thi tự động qua Codex
- **review**: Kiểm tra chất lượng code
- **merge**: Gộp nhánh + cập nhật tài liệu
Dự án vẫn đang trong quá trình thử nghiệm, chưa hoàn chỉnh. Đề xuất mới về việc tích hợp AI vào Git thông qua các lệnh phân công/giám sát trực tiếp.
#Git #Codex #DevTool #AI #PhátTriểnPhầnMềm #CôngNghệMở
https://ww
Show Original Post
zvavybir (@zvavybir@social.zvavybir.eu)
And while we're at it: Also around 300 git commits each for my lecture notes, exercises, and other stuff, so in total ~900.
Show Original Post
scy (@scy@chaos.social)
When using a static site generator, it will often output the rendered website into a subdirectory like "dist" or "site" or something like that.
You might then want to put this directory into a different branch (e.g. "pages") in the same repo in order to push it to {Codeberg,GitHub,GitLab} Pages, or Grebedoc, or whatever.
How do you do that? Check out the repo a second time, rsync the output dir there? No. Just use `git worktree`.
https://scy.name/blog/2025/11/git-worktree.html
Show Original Post