ivanilves / travelgrunt Goto Github PK

Make travelgrunt builds really static.

Read this: https://www.arp242.net/static-go.html

Add asdf version manager support for application releases.

Since we mostly operate on text files inside Git repositories, content search feature in some form would be handy.

Add repository-agnostic, filesystem "bookmarks" mode:

• use global, ~/.travelgrunt.yml config file to store it;
• use this file if outside of Git repo - just use travelgrunt to jump across different paths in filesystem;

It would be nice to have multi-level menus:

1. account menu
2. region menu
3. stack menu (optional) ?

... before going to main menu with end projects.

Add code static analysis to continuously monitor code quality.

Definitely we should have support for version managers like ASDF #7 or traditional package managers like dpkg or rpm, but having a self-update command is a very convenient option as well. It can be a real code inside travelgrunt or a bash alias 🙂

Add [optional] plain Terraform support, e.g. to walk over Terraform module repos.

We could use artificial intelligence to advice user on the most suitable directory navigation patterns!

tg could use $EDITOR variable to open and edit files not only traverse the directories, what do you think @ivanilves ?

Refactor tree and node packages, clarify the responsibilities tree and node packages have.

Add command switch to do cd to the Git repository top level directory.

Add support for rule loading from config file. We need to be able to change operation mode of travelgrunt without recompiling it 🙂

Thank you!

We need to add a better help command in CLI with examples on how to configure various modes,
... or just be lazy and give a link to https://github.com/ivanilves/travelgrunt/blob/main/README.md

Add help instruction to the Makefile and make it default.

We need a better, clearer approach to test these fast-growing packages (config & include).
Current test suite will become unmaintainable very soon, thus new suite should be a priority.

Add homebrew support, so MacOSX users can easily upgrade / manage program versions.

Add strict semantic commit check to avoid commit message chaos

Add third-party code quality and test coverage checks with corresponding repository badges 😎

https://www.runforesight.com/blog/top-5-badges-that-will-show-your-github-repository-is-well-tested-trusted

Sonarqube?

Goverals?

etc