Running bitbucket_erlang_client with the -k command line switch shall force the tool to keep running even if it encounters errors (very useful for verification runs).
This works within a single repo, however when processing a .ymlt/.ymlv file-pair, the tool stops after the first repo with errors instead of trying the template with the next value.
Note: this behaviour happens at least when an exception happens in the tool. I'm not sure about warnings breaking the iteration.
Running bitbucket_erlang_client with the -k command line switch shall force the tool to keep running even if it encounters errors (very useful for verification runs).
This works within a single repo, however when processing a .ymlt/.ymlv file-pair, the tool stops after the first repo with errors instead of trying the template with the next value.
Note: this behaviour happens at least when an exception happens in the tool. I'm not sure about warnings breaking the iteration.