GitHub Release task suggestions

[davidstaheli]

Can you please consider these tweaks to the new GitHub Release task?

1. Tweaks to strings
2. Capitalize "GitHub"
3. Remove input aliases. Feel free to reject this if it's too disruptive. But making the input name match the alias name makes docs generation nicer, starts clean where aliases aren't necessary before the task ships, and keeps names the same between JSON and YAML.
4. Change the service connection input to allow only PAT and OAuth schemes. The "Token" scheme isn't supported by tasks because we have to keep the token private from the agents. :( See below:

"type": "connectedService:github:OAuth,PersonalAccessToken",

[mdmdakbar]

Thanks David for taking your time to review it.

[mdmdakbar]

We used this value as $(action) in instanceNameFormat property below. So that task name can be modified according to action. For e.g. Create GitHub Release or Edit GitHub Release. But Lowercasing the options will lead to create GitHub Release or edit GitHub Release.

[davidstaheli]

@mdmdakbar, ah... I see what you mean. To the user, these values are case-insensitive when used in their YAML pipelines. Most GitHub users will use the typical YAML camel-casing and lowercase the the action value on their own, like this:

- task: GithubRelease@0
  inputs:
    action: create
    gitHubConnection: myConnection

Since most people will lowercase it in their YAML (no matter what casing is used in task.yaml), what would you think about changing instanceNameFormat to have the action at the end, like this?

• GitHub release (create)
• GitHub release (edit)
• GitHub release (discard)

[davidstaheli]

Since GitHub documentation refers to deleting a release, this PR also proposes that we use delete as the action name instead of discard.

[davidstaheli]

Hi @mdmdakbar. I hope I've resolved everyone's feedback on this. I'll merge it based on your approval, but please let me know if I can help change anything later. Thanks very much for considering this PR!