• 0 Posts
  • 351 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle

  • Let’s give it a shot. I live in the suburbs of Lincoln, Nebraska, which is an average-sized college town in the US (about 300k residents):

    • Nearest convenience store: 1.1 miles/1.7km (we often do walk there, takes about 20 minutes)
    • Nearest chain supermarket/big supermarket (they are often one in the same here): Target @ 1.5 miles/2.4km
    • Bus stop: 1.3 miles/2.1km
    • Nearest park: 0.6 miles/965m
    • Nearest public library: 3.5 miles/5.6km
    • Nearest train station: 9.1 miles/14.6km (we don’t really use trains much at all in the US, though)



  • Interactive rebase? There’s no GUI that actually does that well, if at all. And it’s a massive part of my daily workflow.

    The CLI is far, far more powerful and has many features that GUIs do not.

    It’s also scriptable. For example, I often like to see just the commits I’ve made that diverge from master, along with the files changed in each. This can be accomplished with git log --oneline --stat --name-status origin/master..HEAD. What’s more, since this is just a CLI command, I can very easily make a keybind in vim to execute the command and stick it’s output into a split window. This lets me use git as a navigation tool as I can then very quickly jump to files that I’ve changed in some recent commit.

    This is all using a standard, uniform interface without mucking around with IDE plugin settings (if they even can do such a thing). I have many, many other examples of scripting with it, such as loading side-by-side diffs for all files in the worktree against some particular commit (defaulting to master) in vim in a tabpage-per-file, which I often use to review all of my changes before making a commit.






  • I’m sure it’s fine for small-scale usage, but overall it’s extremely inflexible and doesn’t really scale well at all. There’s also a lot of very basic functionality that’s straight up missing. For example, there’s no way to have a global epic priority. You can rearrange epics in an epic board, but the ordering of the epics there is not persisted elsewhere. There were many, many other shortcomings we kept running into.

    Oh, and after a lot of our tickets had been imported (which itself was a huge undertaking since the auto import tools are complete trash), it started to be very slow. It feels like a very unfinished, unpolished product.

    We use Gitlab’s CI/CD features extensively at my current job and it’s very, very nice. That’s what they are actually good at, not project management.