Move monzo_ynab into //tools
Optimizing is difficult: I like flat hierarchies because I don't like directory-hopping, but I also would like a cleaner root for my mono-repo. Bombs away! Well it's that time again, folks: spring cleaning! Here I am musing about a few things that bother me: - Should I use kebab-case or snake_case? - It feels ~confusing to have //tools and //utils. What a //projects? Isn't everything a project? *sigh*
This commit is contained in:
parent
4ed3254709
commit
5add8ddc13
16 changed files with 3 additions and 3 deletions
3
.gitignore
vendored
3
.gitignore
vendored
|
@ -26,9 +26,6 @@ Vundle.vim
|
||||||
# Python
|
# Python
|
||||||
__pycache__
|
__pycache__
|
||||||
*.class
|
*.class
|
||||||
/monzo_ynab/ynab/fixture.json
|
|
||||||
/monzo_ynab/monzo/fixture.json
|
|
||||||
/monzo_ynab/kv.json
|
|
||||||
node_modules/
|
node_modules/
|
||||||
/configs/.config/fish/config.fish
|
/configs/.config/fish/config.fish
|
||||||
/configs/.config/fish/fish_variables
|
/configs/.config/fish/fish_variables
|
||||||
|
|
3
tools/monzo_ynab/.gitignore
vendored
Normal file
3
tools/monzo_ynab/.gitignore
vendored
Normal file
|
@ -0,0 +1,3 @@
|
||||||
|
/ynab/fixture.json
|
||||||
|
/monzo/fixture.json
|
||||||
|
/kv.json
|
Loading…
Reference in a new issue