Casper da Costa-Luis

`commit create`

3

With similar convenience options as `cml pr create`. ``` cml commit create [--skip-ci] [--message=] [--user-=] ``` Example use case: ``` cml ci git commit -a -m "CML commit [skip ci]"...

--publish(-native) proxy error messaging

1

`cml --publish-native --log debug comment create report.md` ```yaml {"level":"debug","message":"Send analytics failed: Cannot read properties of undefined (reading 'startsWith')"} {"level":"error","message":"cannotconnect","stack":"Error: cannotconnect\n at Gitlab.request (/usr/lib/node_modules/@dvcorg/cml/src/drivers/gitlab.js:489:38)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async /usr/lib/node_modules/@dvcorg/cml/src/drivers/gitlab.js 16\n...

As per https://developer.atlassian.com/cloud/bitbucket/rest/api-group-commits/#api-repositories-workspace-repo-slug-commit-commit-comments-post, BB should support commit comments

detect PR from GITHUB_HEAD_REF instead of github.event.pull_request.head.sha

4

drop the `checkout.with.ref` requirement in favour of CML auto-detecting the PR from the `$GITHUB_HEAD_REF` [env var](https://docs.github.com/en/actions/learn-github-actions/environment-variables)? ```diff on: pull_request ... - uses: actions/checkout@v3 - # quite clunky and might not...

issue comments

4

CML version of `gh issue comment`? Use cases: - open an issue on failing job (not just a `cml check` or commit-`comment`) & post a report to it - (ab)use...

handle squash/rebase merges without --force

1

If you always squash-merge, the unsafe `--force` flag is always required. Instead, ideally `gh-clean-branches` should do one of: - GH API query to get the commit hash just before it...

bash: support -- delimeter

5

- fixes #163 [`diff` *sans* whitespace](https://github.com/iterative/shtab/pull/164/files?w=1)

Support `editable_wheel` with `setuptools>=64`

1

On the subject of `pip install -e, --editable` woes, I've seen #697, #370, #436, #616, #585, #579, and also tried #582, https://github.com/scikit-build/scikit-build/issues/546#issuecomment-1196539698, https://github.com/scikit-build/scikit-build/issues/546#issuecomment-1196580256. I think I have a different issue...

- tests: bump pre-commit - replace pkg_resources => importlib.resources

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of...