v0.1.1: A GitHub Action for scheduled runs, and commands default to the current checkout

The Count can now run from a GitHub Action, and without a repository argument he works on the checkout you are in rather than every repository your token can reach.

Added

• A GitHub Action, sweepies/count-patchula, that installs patchula with mise, keeps the cache between scheduled runs, and runs patchula run. It takes token, repositories, all-repos, dry-run, version and args inputs. Pinning the action to a release tag runs that matching version. (#4)

  - uses: actions/create-github-app-token@64ab729a6294000f5aa4a4bc0b73d1f32bc45510 # v3.3.0
    id: app
    with:
      client-id: ${{ vars.PATCHULA_CLIENT_ID }}
      private-key: ${{ secrets.PATCHULA_APP_PRIVATE_KEY }}
  - uses: sweepies/count-patchula@v0.1.1
    with:
      token: ${{ steps.app.outputs.token }}

  The guide covers a single repository and an organization-wide runner that uses --config-dir. Use a GitHub App token, not GITHUB_TOKEN, so the Count's pull requests trigger your checks.

• A patchula skill for coding agents, shipped in the packslip manifest and at skills/patchula. It covers configuring, validating and running the Count.

Breaking Changes

lookup, run and tui no longer process every accessible repository when you give no repository argument. They now use the GitHub repository from the origin remote of the current directory, or its only remote. If the directory is not a checkout of a github.com repository, the command exits with status 2.

To keep the old behavior, pass --all-repos:

# 0.1.0: every repository the token can reach
patchula run

# 0.1.1: the repository in the current checkout
patchula run

# 0.1.1: every repository the token can reach, as before
patchula run --all-repos

Update scripts and CI jobs that relied on the no-argument form to add --all-repos. Naming repositories explicitly (owner/repo) works as before.

Full Changelog: v0.1.0...v0.1.1