fix: resolve GitHub Actions workflow conflicts and deployment issues #24
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.
Summary
This PR fixes critical issues with the GitHub Actions workflows that were causing deployment failures and back-merge conflicts in the Git Flow process.
Problems Addressed
1. Deployment Trigger Issue
deploy.ymlworkflow wasn't triggering automatically when tags were created byrelease-automation.ymlworkflow_dispatchoption as a backup deployment method2. Back-merge Conflicts
3. Duplicate Workflows
backmerge-to-develop.ymlwas redundant with functionality inrelease-automation.yml4. Version Bump Conflicts
package.jsonandCHANGELOG.mdChanges Made
Modified Workflows
release-automation.yml
release-branch-creation.yml
deploy.yml
workflow_dispatchtrigger for manual deploymentbackmerge-to-develop.yml
Testing Recommendations
Create a release branch and verify:
Merge release to main and verify:
Test manual deployment:
Impact
These changes ensure a smooth Git Flow process with automatic conflict prevention, reliable deployments, and reduced manual intervention.