Closed Poorna-Gottimukkula1 closed 7 months ago
Hi @Poorna-Gottimukkula1. Thanks for your PR.
I'm waiting for a coreos member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Can you provide more context on this? It's very rare that an empty commit message is appropriate. :)
If that filename is very user-visible, then it might make sense to templatize that field and give an even more meaningful name.
yes, agree on the templatizing. it would be good to have the version in if possible. when we talked before and i suggested just coreos
, I wasn't clear about also keeping that part (that you originally had).
/ok-to-test
Enhancing visibility of OS's in PowerVS "Volumes" view includes providing additional details. IBM i, for example, names their .raw files "IBMi-\-img.raw".
Task ref: https://issues.redhat.com/browse/COS-2627