We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Builds of tagged commits on AppVeyer should use GitHub Release storage.
Artifacts should be published as Draft releases so we can manually check and update notes prior to public release.
you may tell AppVeyor to create a “draft” release so you can perform any final checks before making it public. -- https://www.appveyor.com/docs/deployment/github/
The text was updated successfully, but these errors were encountered:
As we're moving to GtiHub actions, I think issue is not needed anymore.
Please let us know if you need further information or would like us to take another look at this
See #797
Sorry, something went wrong.
No branches or pull requests
Builds of tagged commits on AppVeyer should use GitHub Release storage.
Artifacts should be published as Draft releases so we can manually check and update notes prior to public release.
The text was updated successfully, but these errors were encountered: