hub VS goreleaser

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities.

parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name # (Uses `command` to bypass wrappers like https://hub.github.com/) ref="$(command git symbolic-ref --short HEAD 2> /dev/null)" || return echo " [$ref]" }

Which will create a new remote with that name (otherwise origin will be used).

It is also less typing.

[1]: https://github.com/github/hub

I alias git to use HUB from GitHub

If you also install Hub https://github.com/github/hub it gives you a git create command, it also has a set of really useful additional CLI utilities.

SCM: Git + Hub (https://github.com/github/hub)

This is my favorite feature of this tool. Because every time I commit something and want to create PR/MR, I have to do a bunch of repetitive clicks here and there. On top of that, sometimes I have to work with GitHub, sometimes GitLab. So even if I wanna use the GitHub CLI tool hub or GitLab CLI tool glab, I am ending up using two different tools. So it's nice when I can open PR/MR just by a shortcut within a second or two regardless of what SCM I am on.

Hub - a wrapper for Git command (Git+Hub=GitHub).

With "xq", I went even further and automated the release process using GoReleaser. To publish a new release, the only thing I need is to create and push the Git tag. The corresponding GitHub Action will trigger a release process, and GoReleaser prepares the binaries and changelog based on declared conventions. The result has a high level of predictability, and no manual work is required.

Things I can't live without in a new Go project in no particular order:

- https://github.com/golangci/golangci-lint - meta-linter

- https://goreleaser.com - automate release workflows

- https://magefile.org - build tool that can version your tools

- https://github.com/ory/dockertest/v3 - run containers for e2e testing

- https://github.com/ecordell/optgen - generate functional options

- https://golang.org/x/tools/cmd/stringer - generate String()

- https://mvdan.cc/gofumpt - stricter gofmt

- https://github.com/stretchr/testify - test assertion library

- https://github.com/rs/zerolog - logging

- https://github.com/spf13/cobra - CLI framework

FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb

We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers

Goreleaser is nice. https://goreleaser.com/

I use goreleaser for packaging my binaries. I'm not currently doing RPM, but it does a lot of services and if you don't hunker down on a single solution, it might help with keeping your releases up to date/in sync.

We also started using goreleaser to build our binaries and package them for linux (and mac universal binaries). Makes building and packaging releases easy.

There's some packaging issues, for example, we've always wanted to publish deb/rpm packages, but never got around to adding it to either promu or completely switching our build tooling over to GoReleaser.

The project is at https://github.com/goreleaser/goreleaser - It can create homebrew taps and all that sort of stuff to make distribution easier.

Building binaries works easily by cross-compiling (just set `GOOS=`) to build for other OSes. If you want a tool to help you with that (and automate more of the release process), you could take a look at https://goreleaser.com/.

More recently, a lot of my pipeline pain is handled by GoReleaser, but before GoReleaser matured, I got up to all sorts of shenanigans to get a workable toolchain, e.g. neilotoole/xcgo.