merge-train-infra

Document GitHub Actions automation internals for merge-train operations.

Updated May 14, 2026
One-click install
npx skills add https://github.com/HabibTorjmen/Blockchain --skill merge-train-infra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-train-infra
Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/merge-train-infra
Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill merge-train-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates uncertainty when modifying complex merge-train infrastructure by documenting how GitHub workflows, CI modes, scripts, and failure notifications interact to move code safely from next into active train branches.

Core Features & Use Cases

  • Workflow orchestration: Covers the full automation lifecycle for merge-train PR creation, PR body updates, next-to-branches integration, auto-merge, branch recreation, and dequeue failure notifications.
  • CI integration details: Explains how merge-train branches map to CI modes, concurrency behavior, instance postfixing, and test history tracking.
  • Contributor-facing operational context: Provides a reference for contributor-needed internal details when adjusting merge-train infrastructure logic or debugging edge cases.

Quick Start

Ask the AI to explain how the merge-train automation uses the hourly auto-merge workflow and CI failure checks to decide when a train branch can be merged.

Frequently Asked Questions about merge-train-infra

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

FAQPage Schema
How does merge-train automation handle PR lifecycle and next syncing in GitHub Actions?

Merge-train automation orchestrates the PR lifecycle by managing PR creation, body updates, and next-to-branches integration using specific GitHub Actions workflow triggers and scripts to move code safely into active train branches.

How do I debug inactivity-based auto-merge and branch recreation wakeups in a merge queue?

Debugging inactivity-based auto-merge requires tracing the failure-gated auto-merge logic and hourly workflow triggers in merge-train infrastructure to understand how CI failure checks decide when a train branch can be merged.

How do merge-train branches map to CI modes and concurrency behavior?

Merge-train branches map to CI modes using specific label mapping and concurrency rules, applying instance postfixing and test history tracking to manage integration behavior across CI integrations.

Why does a PR get dequeued from the merge queue after a CI failure?

A PR gets dequeued because merge-train infrastructure uses failure-gated auto-merge logic, where CI failure checks and dequeue failure notifications prevent unsafe code from moving from next into active train branches.

Can I use Slack notifications to monitor merge-queue dequeue failures in GitHub Actions?

Yes, Slack notifications are integrated into the merge-train automation workflow to alert on merge-queue dequeue failures, providing immediate visibility when CI failure checks block a train branch merge.

What's the best way to document GitHub Actions workflow triggers for merge-train infrastructure?

Documenting merge-train infrastructure requires mapping workflow triggers to the scripts invoked by workflows, detailing CI mode and label mapping, concurrency rules, and instance postfixing for contributor-facing operational context.