skills.rest
dotCMS
dotCMSOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dot-release-backport-lts

Backports closed GitHub issues labeled LTS Next Patch to dotCMS LTS release branches.

950|482|Updated Mar 15, 2012
Search Tags:#release management#Git#cherry-pick#dotcms#gitHub#lts#backport
One-click install
npx skills add https://github.com/dotCMS/core --skill dot-release-backport-lts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dot-release-backport-lts
Source: https://github.com/dotCMS/core/tree/main/.claude/skills/dot-release-backport-lts
Command: npx skills add https://github.com/dotCMS/core --skill dot-release-backport-lts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining long-term support (LTS) release branches requires manually finding fixed issues, locating their merged pull requests, applying diffs, and committing each change to the release branch. This Skill automates that repetitive backporting workflow for the dotCMS/core repository while preventing partial or duplicate backports.

Core Features & Use Cases

  • Automated Issue Discovery: Fetches all closed GitHub issues labeled "LTS: Next Patch" and detects which ones are already recorded in hotfix_tracking.md.
  • Linked PR Resolution: Uses the GitHub GraphQL API and PR search to find every merged pull request linked to an issue, including companion PRs, and applies their diffs in order.
  • Safe Patch Application: Performs dry-run checks, 3-way merge fallbacks, and per-file patch splitting, pausing for manual resolution whenever a patch cannot be applied cleanly.
  • Use Case: A maintainer on the release-25.07.10_lts branch runs the skill to backport all pending LTS patches; each completed issue is committed with a standardized message, pushed, and logged in hotfix_tracking.md, ending with a summary report.

Quick Start

Run an LTS backport for the current dotCMS release branch, or specify a version such as 24.12.27 when not on an LTS branch.

Frequently Asked Questions about dot-release-backport-lts

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

FAQPage Schema
How do I backport GitHub issues to an LTS release branch?▼

Invoke the skill from the dotCMS/core repository while on a release-X.Y.Z_lts branch, or pass the LTS version as an argument. It fetches closed issues labeled "LTS: Next Patch", applies their merged PR diffs, commits, and pushes each one.

How does the skill find pull requests linked to an issue?▼

It queries the GitHub GraphQL API for timeline events (connected, cross-referenced, and closed events) and also searches merged PRs whose body references the issue number. Results are deduplicated and only merged PRs are accepted.

What happens when a patch does not apply cleanly during a backport?▼

The skill stops and reports the blocked files with the full git apply error, then waits for you to apply changes manually. It can also fall back to 3-way merges or per-file patch splitting, and never commits partial work.

Can I run the LTS backport from a non-release branch?▼

Yes, but you must supply the LTS version as an argument, for example 24.12.27. The skill verifies the corresponding release branch exists on the remote and checks it out before processing issues.

How does the skill avoid duplicate backports?▼

Before applying anything, it checks the committed version of hotfix_tracking.md for the issue number. Issues already recorded are marked as already backported and skipped without modifying any files.

Related Skills

Explore More Software Engineering Skills→
smallorbitsmallorbit

release

Create and merge release PRs, tag commits, close issues, and clean RC branches.

Community
Advanced
AzureAzure
27

hotfix-release

Publish npm package hotfixes from Azure TypeSpec release branches with validation and backmerges.

Official
Advanced
HabibTorjmenHabibTorjmen

backport

Automate merged GitHub pull request backporting to release or devnet staging branches.

Community
Advanced
NVIDIANVIDIA
3.7k

release-cherry-pick

Cherry-pick labeled merged PRs into a release branch and open a tracking PR.

Official
Intermediate