Skip to content

Conversation

mooflu
Copy link
Contributor

@mooflu mooflu commented Aug 15, 2023

and upload the artifacts to a "latest" pre-release.

@emako
Copy link
Member

emako commented Dec 6, 2024

Sorry for auto release is not currently considered, which may bring risks.

However, we may consider joining it in the future.

@emako emako closed this Dec 6, 2024
@mooflu
Copy link
Contributor Author

mooflu commented Dec 6, 2024

Ok, it was meant as a replacement for appveyor.yml to do nightly builds. Not sure why you think this is riskier.

@emako
Copy link
Member

emako commented Dec 6, 2024

OK, I mistakenly thought that the latest release would be modified instead of pre-release.

https://github.com/pyTooling/Actions/tree/main/releaser

@emako emako reopened this Dec 6, 2024
@emako
Copy link
Member

emako commented Dec 6, 2024

I am going to test CI result and it runs as expected.

https://github.com/emako/QLTest/actions/runs/12204827007

@emako emako merged commit a164784 into QL-Win:master Dec 6, 2024
@emako
Copy link
Member

emako commented Dec 6, 2024

Thanks a lot!

@mooflu
Copy link
Contributor Author

mooflu commented Dec 6, 2024

If you add a special tag and a matching release it puts the files in the release area. This MR uses "latest". If you don't want that, you can remove that section from the yml.

On my fork I use "experimental":
https://github.com/mooflu/QuickLook/blob/experimental/.github/workflows/msbuild.yml#L72

which then goes to https://github.com/mooflu/QuickLook/releases/tag/experimental

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants