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

Add GitHub action for next releases #62

Merged
merged 7 commits into from
Feb 18, 2025
Merged

Add GitHub action for next releases #62

merged 7 commits into from
Feb 18, 2025

Conversation

Lotes
Copy link
Collaborator

@Lotes Lotes commented Feb 11, 2025

It is a manual workflow_dispatch.

EDIT: I tested it with the on push trigger on my branch.

@kaisalmen
Copy link
Collaborator

@Lotes if you want to test it before merge, add a on push to the next-release. Once you are sure everything works you remove that again and merge. Unfortunately, this is the only way to make it work with new workflow_dispatch.

Copy link
Collaborator

@JohannesMeierSE JohannesMeierSE left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR @Lotes! It looks nice, I have only some minor questions, since I am not very familiar with configurations for deployment 🙂

Copy link
Collaborator

@JohannesMeierSE JohannesMeierSE left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for improving the RELEASE.md @Lotes!

I found a typo and got ideas for slightly different formulations

@Lotes Lotes merged commit 869e166 into main Feb 18, 2025
2 checks passed
@Lotes Lotes deleted the lotes/next-releases branch February 18, 2025 15:57
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.

4 participants