Casper da Costa-Luis
Casper da Costa-Luis
no that would mean losing your local output. `git stash` will save that.
I'm happy following my proposed workflow as it seems transparent & simple to me. All of the steps between `nbstripout --uninstall` and `--install` are either `git` or manual conflict-fixing operations,...
probably worth documenting in the readme & closing this issue though
Specifying a module to cover means it won't hang, but also it won't actually pick up coverage: ```sh pytest --cov=mymod --cov-report=term --nbval tests/test_mymod.ipynb ... tests/test_mymod::ipynb::Cell 0 PASSED Coverage.py warning: Module...
I'm also leaning towards [this](https://github.com/iterative/terraform-provider-iterative/issues/91#issuecomment-1094339203) - `startup_script`: change to expect raw (affects CML) - `startup_script_base64`: new, expects base64 (CML would switch to using this) - error on both defined (conflicts)
I thought this issue about allowing `cml runner launch --cloud-startup-script` to be plaintext?
https://github.com/iterative/cml/issues/1167 indeed
default: `aws`/`az`/`gcp`/`k8s`. Anything else should be an alias.
closing in favour of remaining #389
I think we should put docs about them in https://github.com/iterative/terraform-provider-iterative/wiki at least for now