[#498] Modify Github Workflow to trigger on new tags matching pattern #519
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.
Closes #498.
This pull request addresses Issue #498, focusing on enhancing the GitHub workflow to trigger deployment to the
dev
branch upon the creation of a new tag that matches the specified patternrefs/tags/dev-
. The changes consist of creating a new workflow configuration file,deploy-dev-from-tag.yml
, to automate the deployment process and distinguish between automatic triggering and manual activation. This modification aims to improve automation efficiency and streamline deployment procedures for the repository.The implemented changes introduce a new workflow configuration file,
deploy-dev-from-tag.yml,
enabling the automated triggering of deployments when a new tag following the patternrefs/tags/dev-
is created. Additionally, the workflow has been updated to differentiate between automated and manual activation to provide flexibility in deployment initiation. This adjustment ensures that tag creation events satisfying the specified pattern trigger the workflow automatically, while still allowing manual activation when needed. The enhancements aim to accelerate deployment procedures and maintain control over the workflow activation process.