snap

Coordinate end-to-end branch snap workflows for dotnet repositories.

20.6k|4.3k|Updated Jan 11, 2015
One-click install
npx skills add https://github.com/dotnet/roslyn --skill snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snap
Source: https://github.com/dotnet/roslyn/tree/main/.github/skills/snap
Command: npx skills add https://github.com/dotnet/roslyn --skill snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and automate the Roslyn branch snap workflow and related multi-repo release preparation for dotnet repos.

Core Features & Use Cases

  • Automates multi-branch snaps across main, release/insiders, and release/stable.
  • Updates PublishData.json, Versions.props, SARIF files, and darc default channels as part of a snap.
  • Orchestrates PRs, milestone moves, and post-snap cleanup planning.

Quick Start

Initiate a snap for a target repository by providing the repo name and the current target version, then confirm the proposed plan before execution.

Frequently Asked Questions about snap

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

FAQPage Schema
How do I automate a Roslyn branch snap across multiple dotnet repositories?

Automating a Roslyn branch snap involves orchestrating merges, PublishData.json updates, version bumps, and darc channel changes across main, insiders, and stable branches. You provide the repo name and target version, then confirm the plan before execution.

What files need updating when snapping a Roslyn release branch?

Snapping a Roslyn release branch requires updating PublishData.json, Versions.props, and SARIF files under src/RoslynAnalyzers. It also involves modifying darc default channels and moving milestones as part of the end-to-end workflow.

How does a post-snap cleanup workflow for dotnet repos work?

A post-snap cleanup workflow schedules follow-up actions after a branch snap completes. It handles milestone moves, PR orchestration, and subsequent cleanup tasks across Roslyn, Razor, and related dotnet repositories to finalize the release preparation.

Can I snap both insiders and stable release branches at the same time?

Yes, you can snap insiders and stable release branches simultaneously. The workflow automates multi-branch snaps across main, release/insiders, and release/stable, coordinating version bumps and merges for each branch independently.

What prerequisites are needed before initiating a dotnet branch snap?

Before initiating a dotnet branch snap, you need the target repository name and the current target version. The workflow reads current versions, drafts PRs, and proposes a snap plan that you must confirm before execution begins.

Does the snap workflow handle darc default channel updates automatically?

Yes, the snap workflow handles darc default channel updates automatically. It modifies darc default channels alongside PublishData.json and SARIF file edits as part of the comprehensive end-to-end branch snap coordination.