Repository navigation
DEVOPS-1131: Use ref_name and add release tag validation in python_deploy_prod.yml - #219
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the production Python deployment GitHub Actions workflow to derive the release tag from the workflow’s ref context (github.ref_name) rather than a manual workflow_dispatch input, and adds a fail-fast guard to prevent running the workflow from non-tag refs.
Changes:
- Removed the
workflow_dispatchrelease-taginput and switched tag resolution togithub.ref_name. - Added a
validate-release-tagjob to fail early when manually triggered from a non-tag ref. - Updated concurrency grouping and downstream reusable-workflow inputs to use the resolved tag.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #219 +/- ##
===========================================
+ Coverage 85.78% 86.10% +0.31%
===========================================
Files 18 18
Lines 950 950
Branches 126 126
===========================================
+ Hits 815 818 +3
+ Misses 99 97 -2
+ Partials 36 35 -1 🚀 New features to boost your workflow:
|
Skip the v* tag check for the release event, since the upstream draft-release flow already enforces it, and drop the unreachable else branch since the workflow only triggers on release and workflow_dispatch.
f288162 to
b09a65f
Compare
|
|
DEVOPS-1131 - python_deploy_prod workflow to use tag from revision: no manual input
Use github.ref_name instead of workflow_dispatch input release-tag, and add a validate-release-tag job to fail fast when the workflow is not run from a tag.
Mirrors the change made in MiraGeoscience/simpeg#167.