hub VS resty

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).

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

We have faced several network issue on our backend application written in golang with resty for inter service calls. We have seen large amount of network errors like `EOF, unexpected EOF, http: stream closed` because of which our APIs fail. Have you faced similar issue and what were the solutions you've implemented.

Go-resty makes it a lot easier to create a http client and much more readable for developers.

I don't use the simple http whenever i need to call any API from code . I just use resty its fairly easy to use and logging requests with it is quite easy

What are the advantages over https://github.com/go-resty/resty ? resty has `.R()` request builder.

We need to call PrinterService from the InvoiceGenerator. Therefore, we need an HTTP client in our project. Install Go’s resty HTTP client library with the following command.

Check out https://github.com/go-resty/resty

I used to use the standard http lib, but now I switched to resty https://github.com/go-resty/resty