GitUp VS git-stack

FWIW, the per line staging functionality in GitUp (https://gitup.co/) is quite easy and straightforward. Very lightweight program that you can open via cli (`gitup` when in a git directory)

Not quite true, though while I was there, many fellow employees misunderstood the rules to mean that you couldn't use GPL software on your machine. At least as of a few years ago, the official ruling was that any open-source software _required_ for you to do your job had to be approved by an internal council of sorts, and GPL and AGPL software was right out. You could, however, use any open-source software you wanted (including GPL and AGPL) so long as it was (1) for personal use, (2) not absolutely mandatory for you to do your job (e.g. some niche software or library propping up your employment), and (3) there was some other alternative tool that you could use if necessary.

So, for instance, a GPL-licensed git client like GitUp[1] was fine to use, and didn't require clearance. You could totally also install a newer version of Nano if you wanted, too.

But, the rules _were_ somewhat vague and scary-sounding, so many engineers I worked with took the rules to mean "absolutely no GPL software under any circumstances".

What email is actually talking about is the option to bundle Nano _with the OS_, which Apple can't do with GPLv3 software. That's why for years, macOS has had an absolutely ancient version of bash (before the license was updated to GPLv3), and switched to zsh in newer versions of the OS.

[1]: https://github.com/git-up/GitUp

Gitup \Mac only]) and the command line at the same time. There are some esoteric commands I can’t remember so it’s nice having a GUI to do it and it’s nice having visual feedback incase of a screwup.

I only use it to keep track of certain projects. Gitup (Mac only) is another GUI client I use for visualizing progress and undoing mistakes.

A git client: Fork (paid), GitFox (paid), or Tower (subscription) for git version control. Which one you use is personal preference / price sensitivity. It's Ford vs Chevy. GitUp is free but a little weirder UI, though very powerful.

I typically use the CLI, but GitUp is the best git visualization tool I've ever found (although it's mac-only).

I Ctrl+F'd for GitUp based on the title, it deserves mention here.

It's all-in on Mac, unfortunately.

https://github.com/git-up/GitUp

> GitUp is built as a thin layer on top of a [Mac-only] reusable generic Git toolkit called "GitUpKit"

I thought Windows Sandbox would be more useful but over time I just haven't fired it up... I kind of forgot about it. I do use Hyper-V.

Every Windows user should run WizTree on their personal machines at least once a year to get a lightning fast report on disk space usage. Cleanup should start wih the largest items or you're just wasting your time! https://news.ycombinator.com/item?id=33893815#33894842

Bitvise SSH Server is also now free for personal use. I've been using it for over a decade since it offered simple multifactor authentication before OpenSSH (IIRC) and can block most bots by client identifier (libssh) -- security through obscurity works spectacularly here because OpenSSH does not yet support this. Their free-as-in-beer SSH client is a great GUI for port forwarding, SFTP, etc. but I dislike the built-in terminal's clipboard handling.

A Mac-only recommendation: https://gitup.co a GPL3 Git client with a unique UI and undo. https://news.ycombinator.com/item?id=27579701&p=2#27580659

If you use Pandora, check out the pianobar cli. For Twitch, there is Chatty (+streamlink cli & VLC).

I set up signald with a Google Voice number but haven't continued down the path of automating Signal.

I tried Tailscale (2021?) but it seemed a bit early, couldn't log out yet. So I went with ZerotTier. https://news.ycombinator.com/item?id=30284754

The tool used to visualize Git Tree: GitUp (looking for something better)

git-stack is the most complicated, rewriting history, detecting when a branch was squashed, etc

I used to use aliases but got frustrated with them when dealing with PRs depending on PRs, so I wrote git-stack [0]. Thought I'd share in case you'd find it useful

[0] https://github.com/epage/git-stack/blob/main/docs/reference....

For anyone interested, I've been collecting notes on various tools in this space: https://github.com/epage/git-stack/blob/main/docs/comparison... (granted the page doesn't mention git-stack since that is assumed)

Personally, I rebase my PR branches on top of each other, rather than merge. It creates a cleaner history (if your merge policy allows maintaining branch history). Tired of managing these branches, I wrote a tool to help though there are other tools in this space, like git-branchless and graphite.

git-move and git-branchless do some great stuff, I wish this wasn't focused on the performance side to distract from the real value.

What I find useful is not the performance but this line

> For example, it can move entire subtrees, not just branches

The referenced docs mention other great quality of life improvements that streamline standard workflows (e.g. deleting local PR branches when merged into upstream)

When performance does matter is when the rebase operation is a small part of a larger operation. In my related tool, git-stack [0], I rebase all branches on top of their latest upstream branches along with re-arranging and squashing fixup commits and soon other features. When automating entire workflows, having each part be fast is important for the whole to still have decent performance.

[0] https://github.com/epage/git-stack

audit for security audits - Separate from regular CI since it only matters for specific changes or when new critical issues come out.

You might be interested in git-stack that I've previously announced

Could you comment on https://github.com/epage/git-stack/issues/25 for why it helps to iterate to find the last non-conflicting commit to rebase onto?

git-stack is the result of me being tired of annoyances in the PR workflow and trying to improve it, like

Fixing branches off of branches when applying a fixup commit (not implemented yet)