luyin (@luyin@lgbtqia.space)
(German version below)
I am proud to announce that my Blog is going live (after 5 years of zero work or content on it at all, lol) - I'd be happy if you boost this in your circles :)
(It's _really, really_ very early but I'm going to be posting regularly from now on, and will be updating here and on Linkedin when I publish new posts. Stay tuned!)
There is no comment section on the blog itself - if you would like to give me feedback, feel free to ping me here :)
Today's article is about a time when I introduced git to a team of non-developers. It contains some technical detail for those who have the misfortune to work with UTF-16 files, but it's mostly a story of helping people and learning by doing:
https://blog.blesius.eu/posts/git_utf16-files/
---
Ich veröffentliche endlich (nach 5 Jahren, in denen ich selten daran gedacht oder herumgefummelt habe, lol) meinen Blog, und würde mich über Boosts freuen!
Es ist wirklich noch sehr früh, aber ich habe regelmäßige Updates eingeplant und werde dann hier und auf Linkedin die neuen Posts verlinken :)
Es gibt keine Kommentarmöglichkeit auf dem Blog - wenn ihr mir Feedback geben wollt, pingt mich gerne hier :)
Der Artikel von heute handelt von der Zeit als ich in einem Team von Nicht-Entwickler*innen git eingeführt habe. Er enthält sowohl technische Details, was für diejenigen, die sich mit UTF-16 kodierten Textdateien herumschlagen müssen, interessant sein dürfte, aber zum größten Teil ist es eine Geschichte darüber, anderen zu helfen und etwas beim Ausprobieren zu lernen:
https://blog.blesius.eu/posts/git_utf16-files/
#git #blog #written_entirely_without_AI_because_I_can #software #development
Show Original Post
7328 (@7328@betula.tail3c2d2c.ts.net)
A syntax-aware git merge driver for a growing collection of programming languages and file formats.
Show Original Post
post (@post@programming.dev)
Worktrees: Git's best kept secret (and why you should use them)
https://programming.dev/post/35297555
Show Original Post
codingcoyote (@codingcoyote@floss.social)
For the love of #git use a sane branching strategy. I just got bit again by a merge issue because we mix merge commits and rebasing.
Our flow is terrible:
• Feature Branches use merge commits to pull changes from `main`
• Pull Requests do. Squash/Rebase onto `main`
`main` is Rebased onto `release` when we deploy to production
• Hot fixes are made on `main`, then cherry picked onto `release`
This has caused so many issues.
Show Original Post
firebase (@firebase@mastodon.social)
Tired of cryptic Git commands? 🤯
Say hello to LazyGit! This terminal UI makes staging, committing, merging, and rebasing a visual breeze. Boost your Git workflow without leaving your terminal. 🚀
https://github.com/jesseduffield/lazygit
#git #devtools #opensource #CLI #developer
Show Original Post
skyfaller (@skyfaller@jawns.club)
Finally, if you really need a full code forge, with issue tracking and everything, what is the simplest, most light-weight code forge you can self-host?
Is it Forgejo? "Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!" https://codeberg.org/forgejo/forgejo
That sounds great to me, but is Forgejo simple enough that I won't regret taking on the maintenance burden? Is there something even faster?
#GiveUpGitHub #git #SelfHosting
Show Original Post
skyfaller (@skyfaller@jawns.club)
To avoid self-hosting a full-fledged code forge, you might want to simply store issues in the git repo itself. Have you tried using git-bug, git-issue, or some other decentralized bug tracker?
* https://github.com/git-bug/git-bug
* https://github.com/dspinellis/git-issue
Last time I tried git-bug I failed to import my issues from GitHub and gave up, but maybe it works now, it seems there is a new & more active maintainer.
#GiveUpGitHub #git #BugTracking #issues #SelfHosting #GitBug
Show Original Post
skyfaller (@skyfaller@jawns.club)
Next, have you tried a static site generator for browsing git repos? Here's a list of SSGs for git, sorted by latest commit (fresh to stale):
* reporat https://www.ratfactor.com/repos/reporat/
* git-arr https://blitiri.com.ar/p/git-arr/
* depp https://git.8pit.net/depp/
* itsy-gitsy https://git.trevorbentley.com/itsy-gitsy/file/README.md
* pgit https://pgit.pico.sh/
* stagit https://codemadness.org/git/stagit/file/README.html
* gituwa https://git.mcksp.com/gituwa/
* repo2html https://git.m455.casa/repo2html/
#GiveUpGitHub #git #SelfHosting #SSGs #StaticWebsites #StaticSiteGenerators
Show Original Post
skyfaller (@skyfaller@jawns.club)
Time to discuss self-hosted alternatives to GitHub!
First, has anyone simply put a bare git repo on a server somewhere, pushed via SSH, and called it a day?
https://idiomdrottning.org/hosting-git-repos
Do you really need more than a remote to push to and pull from, for your personal projects? If you've tried this, what obstacles did you encounter and what features did you miss?
#GiveUpGitHub #SelfHosting #git #SSH #BareRepos
Show Original Post
990000 (@990000@mstdn.social)
I just stumbled across a new project that still uses AWS CodeCommit and I'm kind of shocked Amazon has completely discontinued their Git repo product. Crazy to just drop such an important thing.
Show Original Post
GripNews (@GripNews@mastodon.social)
🌗 告別 GitHub：一位開發者的徹底遷移
➤ 為了掌控與獨立，開源開發者選擇回歸簡樸的自我託管之路
✤ https://tomscii.sig7.se/2024/01/Ditching-GitHub
一位長期對 GitHub 及其母公司微軟的發展有所疑慮的開發者，決定將其所有公開原始碼倉庫從 GitHub 遷移出去，並停止使用 GitHub 的服務。他將代碼遷移至自行託管的 Git 伺服器，並強調此舉是為了保有對自己作品的完全控制權，同時也藉此機會轉向更傳統的基於電子郵件的協作模式，以期提高溝通效率並過濾掉低品質的貢獻。
+ 為了技術自主而放棄便利性，這確實需要相當大的決心。我很好奇他如何處理社羣互動的部分。
+ 我很欣賞他對「自己擁有平臺」的堅持，這在現今雲端服務盛行的時代顯得格外珍貴。
#開源 #Git #軟體開發 #GitHub #自我託管
Show Original Post
smartgit (@smartgit@techhub.social)
ChatGPT users: SmartGit 25.1.066 Preview now lets you open Codex Agent directly for the selected branch. Make sure to configure your environment first: https://docs.syntevo.com/SmartGit/Latest/Manual/Integrations/Codex
Show Original Post