Description
Hi
Similar to the /bench tag which was used in the 100 million rows, would it be possible/worth having a /actions-run tag for use in PRs which signifies when it's ready for benches? Sometimes a PR gets pushed and the actions run automatically each push, but sometimes several pushes are needed before it's actually 'ready' for a re-run. It would be good if it simply waited until the submitter indicated it was ready for a full run.
Similarly, a tag of some kind to request only failing tests re-run for action runner efficiency? Such as I just had an action fail due to CI/CD error (it failed to pull the redis image due to pull limits on dockerhub so errored out) yet the other platform tests went through fine, and no changes are needed. It would be good if we could trigger just that one test, without having to do them all and using up the project action minutes allocation.
I'd rate this as low priority/low importance, so if it's not worth doing don't worry about giving me a long answer :D
Description
Hi
Similar to the
/benchtag which was used in the 100 million rows, would it be possible/worth having a/actions-runtag for use in PRs which signifies when it's ready for benches? Sometimes a PR gets pushed and the actions run automatically each push, but sometimes several pushes are needed before it's actually 'ready' for a re-run. It would be good if it simply waited until the submitter indicated it was ready for a full run.Similarly, a tag of some kind to request only failing tests re-run for action runner efficiency? Such as I just had an action fail due to CI/CD error (it failed to pull the redis image due to pull limits on dockerhub so errored out) yet the other platform tests went through fine, and no changes are needed. It would be good if we could trigger just that one test, without having to do them all and using up the project action minutes allocation.
I'd rate this as low priority/low importance, so if it's not worth doing don't worry about giving me a long answer :D