Casper da Costa-Luis
Casper da Costa-Luis
Would be great to have docs on this... and also potentially a new command (`cml pr update` or similar?) See also [SO#70123668](https://stackoverflow.com/q/70123668)
blocked on #1172 ?
I think @tasdomas means ~checking [`$GITHUB_HEAD_REF`](https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables) instead of requiring explicit `checkout.with.ref: ${{ github.event.pull_request.head.sha }}`~ [301 Moved Permanently](https://en.wikipedia.org/wiki/HTTP_301) to #1204
updated the title & description a bit, clearer now?
opened #1223
...and iterative/cml.dev#251
> as the leaking (in the case of AWS) is slightly displayed as a [feature](https://cml.dev/doc/self-hosted-runners#cloud-compute-resource-credentials) example: That's poor wording on the `cml.dev/doc` pages. The intention was to say "users only...
> personally not a fan of the `{}` syntax `-Wnot-using-a-legitimate-feature`? This syntax exists for precisely this use case (short one-liner unlikely to change). > less commonly seen in the scope...
> For the same reason some code files contain line breaks [Still not right](https://simple.wikipedia.org/wiki/False_analogy) - an accurate analogy would be refusing to use line breaks. Refusing to use a feature...
[dropped {} by popular demand](https://github.com/iterative/cml/pull/1165/commits/96cbc0eb45cf1ef7a7a900021bf543de2715d9c5) ~Also pushed some docstring edits after a thorough review (related to https://github.com/iterative/cml.dev/pull/324) - please do check /CC @0x2b3bfa0~ will move to separate PR