[r5n-83] actions command

[deralaxo]

Summary

Add sis actions command for CI/CD automation and cross-platform git provider support (GitHub + GitLab).

New Commands

sis actions init - Generate CI workflows for automated releases

• Auto-detects git provider (GitHub/GitLab) from remote URL
• Interactive workflow selection or use --all flag
• Available workflows:
  • create-stone - Auto-create stone when PR is merged, then create/update release PR
  • release - Publish packages when release PR is merged
• GitHub: Creates individual files in .github/workflows/
• GitLab: Creates .gitlab-ci-sisyphus.yml with include directive instructions

sis actions release-pr - Create or update a release PR from pending stones

• Auto-generates stones from conventional commits since last release
• Merges all pending stones into a single release
• Creates sisyphus/release branch with version bumps and changelogs
• Archives stones to released/<timestamp>/ directory
• Creates/updates PR with sisyphus-release label
• Stores release metadata in currentRelease config for publish-only mode
• Designed to run in CI after PRs are merged

sis roll --publishOnly - Publish from prepared release (no file changes)

• Reads package versions from currentRelease config
• Creates git tags, publishes to NPM, creates git release
• Clears currentRelease after successful publish
• Designed for two-stage CI: prepare on PR merge, publish on release PR merge

GitProvider Abstraction

• Abstract GitProvider base class with implementations for:
  • GitHubProvider - Full gh CLI integration (PRs, labels, releases)
  • GitLabProvider - Full glab CLI integration (MRs, labels, releases)
  • BitbucketProvider - Stub (not yet implemented)
• Auto-detection via detectProvider() based on remote URL
• Commit author uses r5n-bot[bot] for CI operations

Skip Rules

pr.skip - Skip stone creation for specific PRs:

• labels - Skip PRs with specific labels (default: sisyphus-release, skip-stone)
• authors - Skip PRs by specific authors (default: r5n-bot[bot])
• titlePatterns - Skip PRs matching title regex (default: ^chore\(release\):)

commits.skip - Skip commits when auto-generating stones:

• authors - Skip commits by specific authors (default: r5n-bot[bot])
• messagePatterns - Skip commits matching regex (default: ^chore\(release\):, ^chore: add stone)

Changelog Improvements

• Configurable headers: packageHeader and rootHeader templates
• Package-specific release notes filtered by affected packages
• Collapsible format for detailed changes

Bug Fixes

• Single-package repos - sis pr now correctly detects affected packages
• Exit codes - CLI now exits with code 1 on errors, 0 on Cancel/Exit
• Error visibility - Critical git/API errors are now shown (removed excessive .quiet())

Breaking Changes

• Config: release.github → release.createRelease
• CLI: sis roll --github → sis roll --createRelease / -r

New Domain Helpers

• Stone.mergeAll() - Merge multiple stones into one
• Stone.fromJson() - Deserialize archived stones
• Package.applyStone() - Apply stone bumps to packages
• Package.withVersions() - Set old/new versions explicitly
• Commit.fromHash() - Fetch single commit by hash
• Commit.fromMerge() - Get commits from a merge commit
• CommitAnalyzer.buildStoneData() - Convert commit group to stone data

[linear]

R5N-83 [SIS] `actions` command

This command will create workflows that use baked-in actions for example:

sis actions check-stones (or whatever better name for this flow)

Automated Release PR Creation (like changesets/action)
When stones are committed to the repo, a workflow runs this command that creates/updates a "Release PR". The PR contains version bumps, changelog updates

Merging the PR triggers the actual release

Also it could make actions that:

• after merging automatically run sis pr on that PR and commit the stone
  this of course would trigger the other workflow described above
• after the merge of the Release PR would automatically run the actual sis roll command

Sisyphus GitHub Actions Release Flow

Overview

Automated release workflow using GitHub Actions with a two-stage process: Release PR(prepares changes) and Publish (releases to npm/GitHub).

Directory Structure

.sisyphus/
  stones/                       # Pending stones (unreleased changes)
  released/
    2026-03-11T14-30-00Z/       # Archived stones per release (UTC)
      abc123.yaml
      def456.yaml
    2026-03-15T09-00-00Z/
      ghi789.yaml
  config.json                   # Includes currentRelease marker

Flow

1. PR Merges → Stone Created

When a PR merges to main, the sis-create-stone.yml workflow runs:

• Analyzes the PR (commits, affected packages, bump type)
• Creates a stone in .sisyphus/stones/
• Commits and pushes the stone

2. Stone Pushed → Release PR Created/Updated

When stones are pushed to main, the sis-release-pr.yml workflow runs:

• Collects all pending stones
• Creates/updates a sisyphus/release branch with:
  • Bumped package.json versions
  • Updated changelogs
  • Stones moved from stones/ to released/<timestamp>Z/
  • currentRelease written to config (packages + versions + stone IDs)
• Creates/updates a PR with the sisyphus-release label

3. Release PR Merges → Publish

When the release PR merges, the sis-release.yml workflow runs:

• Runs sis roll --publish-only
• Reads currentRelease from config
• Publishes packages to npm
• Creates git tags
• Creates GitHub release
• No file changes, no extra commits

Config: currentRelease

{
  "currentRelease": {
    "packages": {
      "@r5n/sisyphus": "1.2.3",
      "@r5n/cli-core": "0.5.0"
    },
    "stoneIds": ["abc123", "def456"]
  }
}

This acts as a marker for what should be published. If publishing fails, sis roll --publish-only can be rerun safely — it will verify if packages are already published before attempting.

Commands

• sis actions init — Generate workflow files in .github/workflows/
• sis actions release-pr — Manually create/update release PR
• sis roll — Full release (bumps + changelog + publish)
• sis roll --publish-only — Publish from currentRelease (no file changes)

Benefits

• Single commit — Release PR contains all file changes, no cleanup commits after publish
• Rerunnable — If publish fails, just rerun the workflow
• Auditable — Released stones archived in released/ directory
• Reviewable — Version bumps and changelogs visible in PR diff before merge
• Regenerable changelogs — If changelog format changes (config or code), changelogs can be regenerated from archived stones

[ice-chillios]

Thinking of wrapping all of those git actions into some own module but not sure if that's the time :)

[deralaxo]

Felt like there's no need to do that for the universal ones, but it might me useful later to have the logic in one place. Could do that alongside the plugins/modules support PR

[ice-chillios]

We should always add default and throw/log