Adding a Makefile and bumping version of dependency

[javaducky]

Very minor stuff while I was looking around. Figured I'd add a Makefile to make building locally a bit easier.

Don't know enough on the CI setup just yet, so I didn't change the Go version in go.mod.

[imiric]

Thanks for the PR!

It LGTM, but could you please split the changes into separate commits? Maybe 4: Makefile, dep upgrade, .gitignore and README? So that we could easily roll something back if needed.

[mstoykov]

I really don't think the Makefile adds anything - most things in it replace go <command> with make <command> - so maybe add CONTRIBUTORS.md or INSTALLATION.md or update README.md 🤷

I also in general dislike Makefiles in go projects ... because in most cases they add nothing 🤣

[imiric]

Yeah, I don't use them either in Go projects, since I often need to change commands slightly. I would be lost without command history and ^R 😅

But if it helps someone, why not? 🤷‍♂️

[javaducky]

Definitely doesn't add a lot, but does make it nice to make and have formatting, testing, etc. all done with a single command. For me, that's the developer experience win 😄.

As for the addition of a CONTRIBUTORS.md and such, I'm planning to add those across this and extensions.

[olegbespalov]

I'll stay with the @javaducky, the Makefile makes sense. Important to highlight that it's also a tool for organizing the knowledge-sharing inside (and outside) the project.

E.g. today we need run tests using:

go test -cover -race ./...

tomorrow it can be

go test -cover -race -timeout 210s ./...

The other thing is standardization, e.g. we have in may project standard make target make check (which usually test + check), and for example, in my case I have a global git hook, that executes in every repository:

#!/bin/bash

output=$(make -n check 2>&1 | head -1)
if [[ "$output" != *"No rule to make target"* ]]; then
   echo "Running check"
   make check
fi

which shift left the issue detecting and saves me time

[imiric]

Thanks Paul!