release-branch

Create SkiaSharp release branches from main and trigger CI.

5.5k|644|Updated Feb 22, 2016
One-click install
npx skills add https://github.com/mono/SkiaSharp --skill release-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-branch
Source: https://github.com/mono/SkiaSharp/tree/main/.github/skills/release-branch
Command: npx skills add https://github.com/mono/SkiaSharp --skill release-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of release branches for SkiaSharp, enabling a repeatable, auditable release workflow and reducing manual errors.

Core Features & Use Cases

  • Create release/X.Y.Z branches from main to start a release cycle and trigger CI.
  • Auto-detect the next preview version from main and enforce semver rules for branch naming.
  • Enforce branch protection policies and document required actions for submodules and main branches.

Quick Start

Create a release/X.Y.Z branch from main to begin the release workflow and trigger CI.

Frequently Asked Questions about release-branch

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

FAQPage Schema
How do I automate git release branch creation for versioned releases?

You can automate git release branch creation by generating a release/X.Y.Z branch from main, enforcing semantic versioning conventions, and triggering CI pipelines to start the release workflow. This standardizes the process and reduces manual errors.

How does auto-detection of the next preview version work when starting a release?

Auto-detection of the next preview version works by reading the latest version numbers directly from the main branch, applying semantic versioning rules to calculate the next iteration, and using that derived version for the new release branch name.

What branch protection policies and submodule handling actions are required for a release branch?

Required branch protection policies and submodule handling actions must be enforced and documented to safeguard the main branch and correctly synchronize submodules before triggering CI on the newly created release branch.

Can I trigger CI pipelines automatically when creating a release branch?

Yes, you can trigger CI pipelines automatically when creating a release branch. The workflow creates the release/X.Y.Z branch from main and then directly triggers CI to initiate the automated build and release cycle.

What is the best way to manage semantic versioning conventions for release branches?

The best way to manage semantic versioning conventions for release branches is to automatically derive the next version from the main branch and enforce strict semver rules for branch naming, ensuring a repeatable and auditable release workflow.