You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
GitHub supports prefilling issues using query parameters. It would be very useful if this worked when creating new "Releases" too. Then scripts could pre-generate the release notes for new releases based on the commits and just open it for the user to edit and then publish it.
The alternative is using the GitHub API to create the actual release, but this is more complicated and requires either creating a login flow or requiring the user to get an access token, both of which are too much overhead for simple tools.
My specific use-case is being able to open a prefilled "Releases" entry for the user after publishing an npm package version with https://github.com/sindresorhus/np
The text was updated successfully, but these errors were encountered:
GitHub supports prefilling issues using query parameters. It would be very useful if this worked when creating new "Releases" too. Then scripts could pre-generate the release notes for new releases based on the commits and just open it for the user to edit and then publish it.
For example: https://github.com/chalk/chalk/releases/new?tag=v1.0.0&title=Foo&body=Notes would prefill the tag, title, and body fields. Since it works with issues, I kinda expected this to work with Releases too and was surprised when it didn't.
The alternative is using the GitHub API to create the actual release, but this is more complicated and requires either creating a login flow or requiring the user to get an access token, both of which are too much overhead for simple tools.
My specific use-case is being able to open a prefilled "Releases" entry for the user after publishing an npm package version with https://github.com/sindresorhus/np
The text was updated successfully, but these errors were encountered: