Skip to content

Add Railway production deploy workflow triggered by version tags#221

Draft
Copilot wants to merge 2 commits intomasterfrom
copilot/update-deployment-trigger
Draft

Add Railway production deploy workflow triggered by version tags#221
Copilot wants to merge 2 commits intomasterfrom
copilot/update-deployment-trigger

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 19, 2026

Decouples production deployment from push-to-master. Deployment now triggers only when a version tag is pushed, giving explicit control over releases.

Flow: push to master → CI runs tests → create tag v* → deploy to Railway production.

Changes

  • New workflow .github/workflows/deploy-production.yml triggered on push.tags: v*
  • Runs full test suite (flake8 + pytest) before deploying
  • Deploys via Railway CLI using RAILWAY_TOKEN and RAILWAY_SERVICE_ID secrets

Required setup

  • Add RAILWAY_TOKEN (deploy token) and RAILWAY_SERVICE_ID secrets in GitHub
  • Disable auto-deploy from master in Railway dashboard

Usage

git tag v1.2.0
git push origin v1.2.0

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: fedecarboni7 <37885214+fedecarboni7@users.noreply.github.com>
Copilot AI changed the title [WIP] Update production deployment trigger on tag creation Add Railway production deploy workflow triggered by version tags Feb 19, 2026
Copilot AI requested a review from fedecarboni7 February 19, 2026 04:02
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.

2 participants