Deploy

Promote a test branch to main via pull request after tests and lint pass.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/foundry --skill deploy-beekeeper-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Deploy
Source: https://github.com/beekeeper-lab/foundry/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/beekeeper-lab/foundry --skill deploy-beekeeper-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow automates promoting a test branch to main by creating a pull request, running tests, and merging when checks pass, removing manual steps.

Core Features & Use Cases

  • End-to-end PR-based promotion from test to main after automated validation.
  • Integrated quality gates through test runs and lint checks before merge.
  • Use Case: In a collaborative project, teams push changes to the test branch and rely on this skill to safely merge to main once CI succeeds.

Quick Start

Trigger a deployment by asking the AI to promote the latest test branch to main, running tests, and merging on success.

Frequently Asked Questions about Deploy

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

FAQPage Schema
How do I automate merging a test branch to main via a pull request?

Automating a test to main merge requires creating a pull request, running tests and lint validations, and auto-merging once CI checks pass. This workflow coordinates PR creation, quality gates, and cleanup to deliver a production-ready main branch.

Can I run tests and lint checks before auto-merging a git pull request?

Yes, integrated quality gates run tests and lint checks before auto-merging a pull request. The merge to main only proceeds when these CI validations succeed, ensuring code quality before deployment.

What is the best way to promote a test branch to main after CI succeeds?

Promoting a test branch to main after CI succeeds is best handled by an end-to-end PR-based promotion workflow. It coordinates preparation, PR creation, automated testing, merge, and cleanup steps to safely deliver production-ready code.

Does the automated promotion to main require manual approval before merging?

Automated promotion to main requires a single approval to gate the merge. After this approval and successful CI validations, the workflow automatically merges the pull request and runs cleanup steps.

How do I trigger an automated pull request deployment from test to main?

Trigger an automated pull request deployment by asking the AI to promote the latest test branch to main. The workflow then handles PR creation, runs tests, and merges on success without further manual intervention.