Skip to content
New issue

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

Publish to GitHub Releases from AppVeyer #680

Closed
dtchepak opened this issue Jan 24, 2022 · 1 comment
Closed

Publish to GitHub Releases from AppVeyer #680

dtchepak opened this issue Jan 24, 2022 · 1 comment
Labels
build Issues relating to builds: compile, running tests, CI

Comments

@dtchepak
Copy link
Member

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/

@dtchepak dtchepak added the build Issues relating to builds: compile, running tests, CI label Jan 24, 2022
@304NotModified
Copy link
Contributor

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

@304NotModified 304NotModified closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues relating to builds: compile, running tests, CI
Projects
None yet
Development

No branches or pull requests

2 participants