Why is this PR required? What issue does it fix?:
git-release script returns error if release at targeted branch already exists. This PR address this issue.
What this PR does?:
Fix the git-release to validate the error message and return error only if tag creation failed.
Cherry-pick of https://github.com/openebs/libcstor/pull/59
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered and commands you used for testing with logs:
Any additional information for your reviewer?:
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
[ ] Fixes #
[ ] PR Title follows the convention of <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
Why is this PR required? What issue does it fix?: git-release script returns error if release at targeted branch already exists. This PR address this issue.
What this PR does?: Fix the git-release to validate the error message and return error only if tag creation failed. Cherry-pick of https://github.com/openebs/libcstor/pull/59
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered and commands you used for testing with logs:
Any additional information for your reviewer?: Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>Signed-off-by: mayank mayank.patel@mayadata.io