Amit Kumar Das

`chore: #555 - Update Issue template with LTS info` I guess above looks fine. I hope #555 is issue number. Issue may be optional perhaps. Was #555 the PR number?...

Can I set the old commits with GitHub labels like major, minor, chore etc. Will that do without getting too much into git stuff.

@kmova can you please provide your thoughts as well.

@grzesuav Triggers have been set at [quay](https://quay.io/repository/amitkumardas/metac) to build docker images of metac whenever any PR is pushed against [metac repo](https://github.com/AmitKumarDas/metac/). These images are hosted at quay _(similar to dockerhub)_....

Yes. @grzesuav It's the same case when we cut a GitHub release on the repo. This release version is automatically reflected as a tag in the docker image.

Hi @grzesuav Do we need to first tag a 1.0.0 & then add the commit verification? Do you have in mind any commit verificator that can be added to this...

> For semantic release itself, it can be done via : > github action (like https://github.com/marketplace/actions/action-for-semantic-release) > travis ci > what is your preference ? Let us try with github...

> after merging (or before) one of the maintainers should install https://github.com/apps/semantic-pull-> requests - @AmitKumarDas can you do it ? Done with merge as well as installing above app!

@grzesuav Any CI or github actions that makes the entire workflow smooth will be good. I would need help from your side to setup these. Travis CI is used to...

This will be a good idea to follow. Probably a template for examples will be a good starting point. kind, k3s, minikube etc can be placed as separate scripts if...