Casper da Costa-Luis

Results 233 issues of Casper da Costa-Luis

default GH token timeout 24h should be mentioned in CML runner use cases (i.e. use a PAT instead)

documentation
C: ref
C: guide

Current https://cml.dev/doc/self-hosted-runners?tab=GitHub#personal-access-token only covers "[classic](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-personal-access-token-classic)" tokens. Missing: - [ ] [creating GH fine-grained tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token) + [ ] [permissions required](https://docs.github.com/en/rest/overview/permissions-required-for-fine-grained-personal-access-tokens) for each CML command - [ ] [workflow `permissions`](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions) required for...

documentation
p1-important
epic

https://cml.dev/doc/self-hosted-runners#environment-variables belongs in a separate page as it's not specific to self-hosted runners (e.g. includes PAT permissions necessary for CML reports). Related: #400

documentation
enhancement
p1-important
external-request
C: guide

### v1 ```mermaid graph TD start[How to Install CML] --> Dq{Using your own Docker image?} Dq-->|Yes| Gq{Using GitHub?} Gq-->|Yes| SC["iterative/setup-cml@v1"] Gq-->|No| MI[cml.dev/doc/install] Dq-->|No| Nq{Using a GPU?} Nq -->|Yes| DG[iterativeai/cml:0-dvc2-base1-gpu] Nq...

documentation
external-request
C: guide

e.g. a GitLab user might delete `tags: [cml]` without realising it is necessary when using `cml runner launch --labels=cml`

documentation
p1-important
external-request
C: guide

https://cml.dev/ "CML Use Cases" only has GH & GL (missing BB) runners. - [x] add Bitbucket tab to https://github.com/iterative/cml.dev/blob/master/src/components/pages/Home/UseCasesSection/index.tsx (#362) + [ ] sort out demo repos https://github.com/iterative/cml-examples-dev/issues/9 + [x]...

documentation
p1-important
epic

## p1 - [x] https://github.com/iterative/cml/issues/514 - [ ] update landing page https://cml.dev + [ ] clear message around 2 major use cases: `runner` & `report` * [ ] report: basic...

documentation
p1-important
epic

Effectively combine: - [`dvclive.Live(report="md")`](https://dvc.org/doc/dvclive/api-reference/live#parameters) - [`cml comment create --watch --publish dvclive/report.md &`](https://cml.dev/doc/ref/comment#--watch) + or maybe `cml comment update --pr --watch --publish dvclive/report.md &`

documentation
epic

Quite a few instances in https://github.com/search?l=Text&q=org%3Aiterative+sklearn&type=Code See e.g. https://github.com/iterative/example_cml/pull/256, https://github.com/iterative/cml_dvc_case/pull/23

documentation
p1-important
bug

follow-up to #247 - make better use of `usage` blocks (include options in full so they get hyperlinked properly)

documentation
enhancement
C: ref