why not just setting up github enterprise? i mean it's still an infra to take care but if you are willing to pay for it, you may as well? from my experience the other git forge doesnt provide the same feature sets and api as github, like gitlab ci is actually pretty limited compared to GHA, there is no concept of github apps for other providers too, but maybe you just want a code hosting..

We have both GHE as well as GH.com - and, i genuinely couldn't tell you which of the two blows up more often.

I compare this to the request and httplib in python, request library is vastly superior in usability but both do the same..

the new git history command seems to be useful for quick reword, altho since i use lazygit/magit i don't really see much of a problem to me

Wish reword took a commit range though

I had to check and `jj describe` does. You get all the commit messages in a single file to edit, with headers separating them.

I replaced my custom nightmare of nixos on rpi5 (too much disk space used, too much IO used for raspberry) to a raspbian+arm+homebrew and i could not be happier

Oh no, i was going to setup the same, would you mind sharing more details? I just need a text-only linux for basic stuff. Do you share your nixos config anywhere?

Sadly, I came to the same conclusion. This is also why I no longer buy raspberry pis.

with the web browser you see a preview of the link ! not with most terminal i have tested

Just noting that Ghostty shows a preview in the bottom corners just like a browser.

Alacritty shows a preview at the bottom by default (sounds similar to ghostty). Looked to me like WezTerm doesn't though.

gh-poi plugin is a must if you manage a lot of github pr and want to easily clean the branch attached to it when pr is merged https://github.com/seachicken/gh-poi

reading the code, what make you think it was vibe coded?

I gave up and moved to cloudfare for my static blog, it was too much of a pain to track the spammers. (i am not proud of using big$corp)

I use git worktree for that... it's great

That's a fair point. I think the author intended the post to be a treasure trove of ideas for your own scripts, not as something to blindly include in your daily workflow.