bump-ark

Opens or updates Positron PRs that bump the Ark submodule via the GitHub API.

4.2k|179|Updated May 24, 2022
One-click install
npx skills add https://github.com/posit-dev/positron --skill bump-ark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-ark
Source: https://github.com/posit-dev/positron/tree/main/.claude/skills/bump-ark
Command: npx skills add https://github.com/posit-dev/positron --skill bump-ark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Positron's Ark submodule in sync requires manually creating PRs, writing descriptions, collecting release notes, and tracking which issues get closed. This Skill automates the entire bump workflow through the GitHub API without touching a local clone.

Core Features & Use Cases

  • PR-tracked bumps: Point the submodule at an Ark PR's head while it is open, then finalize the same Positron PR to the merge commit once the Ark PR merges, on a single fixed branch.
  • Latest-main bumps: Track posit-dev/ark@main on a dedicated branch, advancing it in place with fast-forward commits and an author guard that prevents clobbering a colleague's open bump PR.
  • Automated PR descriptions: Generates Closes lines, e2e test tags, aggregated release notes from bumped Ark PRs, and a first-parent commit list that collapses unmerged stacked PRs into one line each.
  • Use Case: After merging an Ark PR, run the bump to update the Positron PR so it points at the merge commit with refreshed release notes and issue references, ready for CI and review.

Quick Start

Ask the assistant to run /bump-ark with an Ark PR number or "main" plus any extra @: e2e tags to open or update the Positron submodule bump PR.

Frequently Asked Questions about bump-ark

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

FAQPage Schema
How do I bump the Ark submodule in Positron to a specific Ark PR?

Run the bump script with the Ark PR number, for example /bump-ark 1234. It opens a Positron PR on branch bump-ark/pr-1234 pointing at the PR head, and re-running after merge finalizes it to the merge commit on Ark main.

How do I bump the Ark submodule to the latest main commit?

Pass "main" as the target instead of a PR number. The script tracks posit-dev/ark@main on the bump-ark/main branch and advances the existing open bump PR in place with a fast-forward commit when one exists.

Does the bump script require a local clone of the Positron repository?

No local clone is needed. The script is fully API-driven through the gh CLI, creating commits, trees, refs, and PRs via the GitHub API, so it never reads or modifies a working tree and never force-pushes.

What happens if a colleague already owns the open main bump PR?

The script refuses to advance a main bump PR owned by someone else and exits with code 3, reporting the owner and PR URL. Only re-run with --confirm after the user explicitly approves advancing that person's PR.

Can I preview the bump PR description without creating anything?

Yes, pass --dry-run to print the assembled PR body to stdout. Only read-only gh calls run, so no branch, ref, or PR is created or modified, letting you review the Closes lines, tags, release notes, and commits first.

How are stacked Ark PRs handled in the bump PR description?

The script detects stacks by matching each PR's base branch against the head branch of another open PR down to Ark main. Each PR in the stack collapses to one line in the commits section, and release notes cover the whole stack.