Adding a workflow for managing releases#77
Merged
ricardogsilva merged 2 commits intoOSGeo:mainfrom Apr 21, 2025
Merged
Conversation
ricardogsilva
force-pushed
the
70-setup-automated-github-releases
branch
from
00f9c3a to
ba08729
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a workflow for managing GitHub releases.
The added workflow is called whenever a new tag with pattern
v*is pushed. It reuses the existingci.yamlworkflow for building a Python package and then creates a release with it.