Verified:GitHub

cicd

Guide Megatron-LM CI/CD operations with PR label-driven test scopes and GitLab pipeline triggers.

Updated May 23, 2026

Search Tags:#gitlab ci #cicd #github workflows #megaton-lm #ci failure triage #pr labels #artifact logs

One-click install

npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill cicd-yo-steven

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cicd
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/Megatron-Core/cicd
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill cicd-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of unclear CI/CD behavior by showing how Megatron-LM’s CI pipeline is structured, how PR labels determine test scope, and how to trigger and investigate CI failures quickly and correctly.

Core Features & Use Cases

CI pipeline structure: Maps the end-to-end workflow from pre-flight configuration through container build/test parsing to the final pass/fail gate.
PR label decisioning: Provides a deterministic label-to-scope/n_repeat/lightweight mapping and guidance for choosing the right labels based on changed paths and risk.
Internal CI triggering: Documents how to trigger the internal GitLab pipeline from a branch programmatically (including required setup).
Failure investigation workflow: Explains how to locate the PR from a CI branch, stream logs, download per-rank artifacts, and classify root-cause categories (lint, container build, unit, functional, flaky).

Quick Start

Use the cicd skill when a PR has a failing CI run and you need to determine the correct scope label to apply, trigger the internal pipeline again, and trace the failure by inspecting the uploaded per-rank logs.

Frequently Asked Questions about cicd

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

FAQPage Schema

How does Megatron-LM CI pipeline structure work for PR label-driven test scope?▼

Megatron-LM CI pipeline structure maps the end-to-end workflow from pre-flight configuration through container build and test parsing to a final pass/fail gate. PR labels deterministically map to test scope, n_repeat, and lightweight execution based on changed paths and risk.

How do I trigger internal GitLab CI for Megatron-LM from a branch programmatically?▼

To trigger internal GitLab CI for Megatron-LM, you must use the correct branch naming convention and complete the required setup. This programmatically initiates the internal pipeline from your specific branch to run the configured test stages.

What is the best way to investigate CI failures and locate per-rank logs in Megatron-LM?▼

Investigating CI failures in Megatron-LM involves locating the PR from the CI branch, streaming logs, and downloading per-rank artifacts. This allows you to classify root-cause categories across linting, container builds, unit, and functional tests.

How do I select the correct PR labels for changed code paths in Megatron-LM?▼

Selecting correct PR labels for Megatron-LM requires evaluating changed paths and risk. A deterministic label-to-scope mapping guides you in choosing appropriate labels that trigger the necessary lightweight or comprehensive test suites.

Why does my Megatron-LM CI run fail and how do I classify the root cause from artifacts?▼

Megatron-LM CI failures are classified by inspecting uploaded per-rank logs and artifacts. Root-cause categories include lint errors, container build failures, unit test issues, functional test breakdowns, and flaky tests.

Can I use this CI/CD guidance for GitHub workflows or is it limited to GitLab CI?▼

This CI/CD guidance applies specifically to Megatron-LM pipelines using internal GitLab CI. It focuses on GitLab CI triggering, branch naming, and artifact-based failure investigation rather than general GitHub workflows.