add `cml-send-comment --update`
See original GitHub issueA new --update
flag would try to overwrite an existing comment rather than post a new one.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
`cml send-comment --update`: Raises 'commit_id has been ...
When calling cml send-comment --update from a python script using subprocess.run, the following error is being raised: "HttpError: ...
Read more >comment | CML
Update the last CML comment instead of creating a new one. If no previous comment is found, create a new one. cml comment...
Read more >@dvcorg/cml - npm
What is CML? Continuous Machine Learning (CML) is an open-source CLI tool for implementing continuous integration & delivery (CI/CD) with a ...
Read more >How do I get rid of the http error when I try to cml send comment
GITHUB_TOKEN }} run: | python -m pip install --upgrade pip pip install ... that I get every time I commit with cml send...
Read more >@dvcorg/cml: Versions | Openbase
Add cml runner --driver=bitbucket support for Bitbucket Cloud Pipelines (#798) ... Add cml-send-comment --update (#581) Update maintainer in Dockerfile ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’d say that’s a completely different feature which we need a separate issue for (
cml-send-comment --skip-unchanged
or similar) even though the implementation PR may close both issues.They work different, cml-pr creates a pr but does not send a SHA comment. Just only the PR description. And cml-pr is never going to reuse the pr. If you use it you will have a PR using current SHA, if happens that you are reusing SHA (repeat workflow) is returning the PR already created for that commit if exist or create if closed (treated as not existing).
Short version. One commit -> one PR