multiple `cml pr` runs
See original GitHub issueIf the data is changed after a PR it’s going to run again generating strange branch names.
experiment-cml-pr-da72cf16-cml-pr-da72cf16-cml-pr-da72cf16
Things to consider:
- If we revert the state use
send-comment
to comment into the new PR viacml send-comment --pr --commit-sha HEAD
wont work - Do not take into account current branch name to avoid concatenation
- Take into account file changes to generate the branch name also we have to consider #792
I wonder if is practical to fix it, I mean, should cml pr
allow double execution? Which ones would be those plausible scenarios?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
cml pr: is racy, generates a PR for different submissions · Issue ...
I am not quite sure here why cml is creating a PR with content that is already in the repo (even if the...
Read more >comment | CML
By default PR comments are created, with a fallback to creating commit comments. ... Repeatedly running cml comment create may produce too many...
Read more >The Progression of Chronic Myeloid Leukemia to ... - NCBI
Myeloid leukemia comes in two major forms, including acute and chronic. · The genetic changes between the two chromosomes involve a shortening of ......
Read more >CML Installation Guide - Cisco Modeling Labs 2.4 - Document
When you run a network topology simulation in CML, each node in the topology runs as a VM on the CML server. When...
Read more >CML Monitoring, Chronic Myeloid Leukemia Patient Resource
As a CML patient, if you do not monitor your disease, you run the risk of ... Monitoring uses multiple lab tests. 3...
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
@casperdcl not really that complex, assuming that we are not rolling back the only issue here is more:
I would not consider it even an epic in terms of big.
@0x2b3bfa0 Im attacking them in a PR