feat: output URLs to prefilled GitHub release forms when executing melos version

[Almighty-Alpaca]

Description

This PR implements a basic type of GitHub release creation. This is done by generating a URL to the form with prefilled values as query parameters, which is displayed at the end of the melos version command as clickable links. For more info see #277.

The following example was executed right after this commit (on my main branch):

Terminal Output

Generated Link

Members of this repository can just click the link to try it out, everyone else has to change the URL to their fork first. Nothing is created by opening the link unless you publish or save the release.

https://github.com/melos/melos/releases/new?tag=melos-v2.8.0&title=melos+v2.8.0&body=%23%23+2.8.0%0A%0A+-+%2A%2AFIX%2A%2A%3A+only+include+normal+dependencies+of+transitive+dependencies+%28%5B%23387%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fissues%2F387%29%29.+%28%5Be0659e97%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fcommit%2Fe0659e976ad2d9eef90f611fa012a51e14880657%29%29%0A+-+%2A%2AFIX%2A%2A%3A+return+type+of+%60promptChoice%60+%28%5B%23391%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fissues%2F391%29%29.+%28%5B54004993%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fcommit%2F54004993c980a204533980508bb2c03b27fe45fc%29%29%0A+-+%2A%2AFEAT%2A%2A%3A+Implement+creating+URLs+to+prefilled+GitHub+release+forms+when+executing+%60melos+version%60.+%28%5B1fd990b1%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fcommit%2F1fd990b1cc2c853c906737863f4ad52dfbd47d99%29%29%0A+-+%2A%2AFEAT%2A%2A%3A+add+%60--dependent-preid%60+option+%28%5B%23388%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fissues%2F388%29%29.+%28%5Bb6201364%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fcommit%2Fb6201364dd951db39ab422b6baaa812cef8b83fd%29%29%0A+-+%2A%2ADOCS%2A%2A%3A+add+%60flutter_html%60+to+projects+using+Melos+%28%5B%23389%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fissues%2F389%29%29.+%28%5B4e3a4447%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fcommit%2F4e3a4447b41973eb4b779b096a0dbdfcf2a3188c%29%29%0A+-+%2A%2ADOCS%2A%2A%3A+add+yak_packages+reference+to+docs%2Findex+%28%5B%23381%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fissues%2F381%29%29.+%28%5B9b366fd9%5D%28https%3A%2F%2Fgithub.com%2Finvertase%2Fmelos%2Fcommit%2F9b366fd917792dbdde1ed59a51beefd46bb88c57%29%29%0A%0A&prerelease=false

Unedited release created from generated URL

Type of Change

• ✨ feat -- New feature (non-breaking change which adds functionality)
• 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
• ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 refactor -- Code refactor
• ✅ ci -- Build configuration change
• 📝 docs -- Documentation
• 🗑️ chore -- Chore

[CLAassistant]

All committers have signed the CLA.

[blaugold]

Basically LGTM, besides the one comment.

I would also put this behind a flag for melos version, e.g. --git-host-release-url and short -r. There are potentially multiple long URLs that get printed and might confuse/annoy users that don't use them.

[Almighty-Alpaca]

I would also put this behind a flag for melos version, e.g. --git-host-release-url and short -r. There are potentially multiple long URLs that get printed and might confuse/annoy users that don't use them.

Should the flag be enabled or disabled by default?

[blaugold]

I meant disabled by default. My gut feeling is that this is more of a specialized feature, only some users take advantage of, but I might be wrong.

An alternative to the command line flag is an option under command/version in melos.yaml.

[Almighty-Alpaca]

Small design note: I've for release.enabled: true instead of release: true to leave room for other release related configurations in the future, e.g. when implementing automatic release creation.

I've also gone ahead and added the new options to the documentation.

[blaugold]

Thanks for also updating the docs!

I've clean up a few things, including renaming --git-release-url to --release-url and putting the option in melos.yaml under command/version/releaseUrl. We eventually would like to make all command options configurable in melos.yaml and maintaining the same structure and names will make that easier.

[Almighty-Alpaca]

Thanks 👍