[X] I have verified this is the correct repository for opening this issue.
[X] I have verified no other issues exist related to my request.
Is Your Feature Request Related To A Problem? Please describe.
No response
Describe The Solution. Why is it needed?
When/if we need to publish a release manually, we have to call a task called Publish-GitHub-Release. After support for GitLab was added, this makes no sense to have this name anymore.
As such, I suggest renaming this task to instead be Publish-Release-Notes (This follows the same naming scheme as used for Export, and Creation).
To keep backwards compatibility, we can keep Publish-GitHub-Release around as an aliased task instead.
Checklist
Is Your Feature Request Related To A Problem? Please describe.
No response
Describe The Solution. Why is it needed?
When/if we need to publish a release manually, we have to call a task called
Publish-GitHub-Release. After support for GitLab was added, this makes no sense to have this name anymore.As such, I suggest renaming this task to instead be
Publish-Release-Notes(This follows the same naming scheme as used for Export, and Creation).To keep backwards compatibility, we can keep
Publish-GitHub-Releasearound as an aliased task instead.Additional Context
No response
Related Issues
No response