Refactor and CI

[obalunenko]

With this PR I add the following enhancements:

• Follow Go community project layout https://github.com/golang-standards/project-layout
• CI/CD support for automation code checks and delivery release artifacts (executables for all platforms that could be downloaded)
• Add makefile automation
• Helper scripts for compiling, linting, and releasing the application

PS more refactor in next PRs

[obalunenko]

@eleby, Could you please review this PR? 🙏🏻

[eleby]

@eleby, Could you please review this PR? 🙏🏻

Of course ! Thanks for the PR ! 😉

[eleby]

I don't know much about dockers and makefiles, but doesn't this mean we won't be able to compile if this docker repo is down someday ? Also, it seems this repo has the name of your company. I don't know if it is relevant to use your company's docker repo here.

[eleby]

If you mark this as resolved please provide an answer about it so I can know if you will fix it

[eleby]

You added lots of things I really don't know about;

Could you update the readme to write a doc about the functionnalities that were added ? It seems like the installation and compilation are completely different with this version, I am a little lost. I'd love to have time to learn about every tool you added and especially what they change in the program use but I don't unfortunately :/

Anyway, great job about all these changes. Can't wait for these informations and the answers to my comments !

[obalunenko]

You're always welcome;) Thanks for your review!
Sure, I'll update the readme
There are no changes in functionality. Only CI/CD - now users no need to install go and build themselves this tool. After you add the tag https://semver.org/ and push it to remote - CI will be triggered and build binaries for all os/arch and publish them on GitHub repo page under releases

You can check example of releases how they will be look)
All artifacts and release notes generated automatically on ci/cd
https://github.com/obalunenko/instadiff-cli/releases

[eleby]

Okay ! So -sorry again for being a beginner in these aspects-, how does it work ?
If I understand correctly, you have to provide a version number and it creates the binaries to be listed on the Github release page. But where do you provide this version number exactly ?

I will wait for your explanations, readme update and fix on the docker package line. I like the idea of improved releases, I hope to understand everything better so I can merge the PR.