Reducing binary size in the build
Saw that http://plugins.drone.io/drone-plugins/drone-gitea-release/ can probably sort our release uploading for us.
could use this for our github mirror…
Setup Contributing.md and pre-commit hooks
Adopt Conventional Commits as standard to all commits
Saw that we can run a CI check that'll lint the commit messages for format:
Looks good but I worry about the effects of doing that…
godotenv multiline env vars and unexpected tokens
I think moving to Viper and then doing what makes sense for the situation is the best way forward sindi it seems to support everything. I will move it to Viper and then we can work on the config…
a60ebf8710
tests: around 60% code coverage for config package
cfe2f70151
refactor: moving logging to command functions
bd9bc530d1
faet: a draft version of the app ls command
f7059dbe98
refactor: filesystem io
8c5e25bd01
chore: updated gitignore; added vscode settings
37c06c82bf
feat: added error to GetContextEndpoint
a2bb0ed027
test: added the first test
38f610bdec
feat: abra server ls
e13948f37e
docs: added todo list for the port
d1f7e8011d
refactor: Moved table function to fornatter
2134f57dd0
WIP: Messy code that is mostly just testing
6c748922b4
feat: added context flag to make dev easier
b9e06f2310
feat: added util formatting for the cil
be46695d82
feat: added flags to base command
Adopt Conventional Commits as standard to all commits
I go into detail about the reasoning behind commits, inspired by this blogpost https://dhwthompson.com/2019/my-favourite-git-commit.
My recent commit is an example of what I strive to do.…
Adopt Conventional Commits as standard to all commits