deploy

Deploy the latest master branch to production with a version tag.

23|4|Updated Sep 5, 2013

Search Tags:#automation #git #production #release #deploy #tagging

Ready to run

npx skills add https://github.com/drn/dots --skill deploy-drn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/drn/dots/tree/main/agents/skills/deploy
Command: npx skills add https://github.com/drn/dots --skill deploy-drn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of deploying the latest changes from the master branch to production, including version tagging and pushing to the production branch.

Core Features & Use Cases

Automated Version Tagging: Creates a new version tag based on the latest commit on the master branch.
Production Deployment: Pushes the new tag and updates the production branch.
Use Case: When you need to release a new version of your software, use this Skill to ensure a consistent and automated deployment process.

Quick Start

Run the deploy script to deploy the latest master to production with a version tag.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy the latest master branch to production with a version tag?▼

To deploy the latest master branch to production, this Skill automates fetching the latest changes, creating a new version tag, and pushing that tag to the production branch. It validates successful tag creation and remote presence before completing the deployment.

What is the best way to automate Git tagging and production releases?▼

Automating Git tagging and production releases is handled by fetching the latest master commit, applying a version tag, and pushing updates to the specified production remote. This ensures a consistent, automated deployment process without manual Git commands.

Can I use this automated deployment process if my repository has multiple remotes?▼

Yes, the automated deployment process supports multiple remotes by validating remote presence and pushing the new tag and production branch updates to the specified remotes configured in your Git environment.

What happens if version tag creation fails during the production deployment?▼

If version tag creation fails during the production deployment, the Skill validates successful tag creation and halts the process, preventing an incomplete release from being pushed to the production branch.

Do I need any external dependencies to automate pushing tags to the production branch?▼

No external dependencies are required to automate pushing tags to the production branch. The Skill operates using built-in scripts to handle Git operations including fetching, tagging, and pushing to your specified remotes.

Why does my automated production deployment require fetching the latest master commit?▼

Fetching the latest master commit is required during production deployment to ensure the new version tag accurately reflects the most recent changes and that the production branch is updated with the correct state.