Closed jwoertink closed 3 years ago
Yup, agree. It's a side effect of how empty documents are interpreted.
A workaround that should work is to have dependencies key always present.
Or use another filename shard.override-template.yml
(?) .
Yeah, if I just make it contain the same version the main one does, it works as a workaround. I might try to see if I can get github actions to not export SHARDS_OVERRIDE if the file is empty or missing or something 😅
You can use the following as a placeholder. Not great, though.
dependencies: {}
# Uncomment if you need to override
# dependencies:
# lucky:
# github: luckyframework/lucky
# branch: master
Ah, ok. Yeah, I was trying a few different combos that weren't working, but that's good to know. Thanks!
If you have an override file that you want to commit to your repo, but you don't always need it to contain info, you might just comment out stuff to start. This causes this error:
Where my file is formatted like this:
oh... actually just to double check, I tested with a blank file, and that doesn't work either