release

currently doesn't work when freshly set up, because GitHub added OAuth access restrictions. If you install fresh and try to use it with a GitHub organization, for example, it will render this error: When logging the internal error that's causing this, it shows additional details: That means, in order for to work in the first place, it now has to support this scenario. Either by changing the way it authenticates, or by at the very least (as an immediate solution, before the real one gets implemented) rendering a special error in that case and linking to this documentation page that GitHub provides.

In addition to https://github.com/vercel/release/issues/193, another major bug appeared in , which is, from my perspective, completely blocking the workflow, and making unusable: When using on a new repository for the first time, it won't respect any existing releases that might've been created in the list of GitHub releases already. For example, in the screenshot below, I ran to create version in this repository, which, as you can see on the link, already has a bunch of existing releases that were created on different devices a longer time ago. What created, unfortunately, is a new release that said "Initial release", which makes no sense.

I've got GHE compatibility working in a fork I created, and was wondering if that is something you'd be open to accepting a PR for? Or is that something that you'd expect developers to fork-and-maintain their own version? The configuration variables I had to override were: for GHE domain for the api root path (typically ) And probably these too, but haven't confirmed yet: to replace zeit reference for custom oauth integration for customizing the oauth server endpoint Let me know what you think! I don't mind keeping a fork but would like to help contribute if that's something you eventually want.