Skip to content

Releases

spec-kit-ghp 0.1.2

Choose a tag to compare

@praveenlavu praveenlavu released this 16 Nov 15:03

spec-kit-ghp 0.1.2

Your AI agent does the GitHub Projects grunt work. You press yes. A Spec Kit extension, workflow and bundle that take a GitHub story to an open pull request, and close it after the merge, with a preview and your yes before every GitHub write.

A small fix release. Nothing is removed. The live test records are in docs/evidence.

Install

pipx install git+https://github.com/praveenlavu/spec-kit-ghp.git@v0.1.2
specify extension add ghp --from https://github.com/praveenlavu/spec-kit-ghp/releases/download/v0.1.2/spec-kit-ghp-extension-0.1.2.zip

Or install the extension and the workflow together from the bundle ghp-0.1.2.zip; the README has the steps.

Files

File SHA-256
spec-kit-ghp-extension-0.1.2.zip 21dc228f99fbf9b8768b6f75e889be2bb99c68ed9b5237951276e33e9dedfbda
ghp-0.1.2.zip 5c210249d649ceeebfbae1d10f1a693f4b7ba73a45a77635b6113fd2a7b33b61

What changed

Fixed:

  • A second ghp push --apply of the same story on the same machine waits for the first (up to 300 seconds, then it stops with exit 2) and then reads again. Before, two runs started together created every task twice. Two runs from two different machines at the same instant can still do that; GitHub gives no way to prevent it.

The rest is documentation. The full list is in the changelog.

spec-kit-ghp 0.1.1

Choose a tag to compare

@praveenlavu praveenlavu released this 13 Nov 15:57

spec-kit-ghp 0.1.1

Your AI agent does the GitHub Projects grunt work. You press yes. A Spec Kit extension, workflow and bundle that take a GitHub story to an open pull request, and close it after the merge, with a preview and your yes before every GitHub write.

This is a fix release. It follows the live test campaign of 0.1.0: the results are in docs/evidence.

Install

pipx install git+https://github.com/praveenlavu/spec-kit-ghp.git@v0.1.1
specify extension add ghp --from https://github.com/praveenlavu/spec-kit-ghp/releases/download/v0.1.1/spec-kit-ghp-extension-0.1.1.zip

Or install the extension and the workflow together from the bundle ghp-0.1.1.zip; the README has the steps.

Files

File SHA-256
spec-kit-ghp-extension-0.1.1.zip 24f87a15f8ce3b21db462f1599cebe9d087ab7e3ca71030e36efc97c8cd77488
ghp-0.1.1.zip 08a09a4706898c82d3a0f35b4d44a80801c04214da0320ef24d49a926971bd86

What changed

A fix release. Nothing is removed. Read the note on ghp done before you upgrade.

Fixed:

  • In comment mode, ghp done can now close a story. Run ghp approvals check <n> --gate approve-done after the approver's /approve to record the approval, then ghp done <n> --apply. The approver must be another account than the one ghp runs as. Link-on-merge still cannot close a story in comment mode: keep close-story: false there.
  • ghp gate reads test ids written in backticks in section 3 of the ledger (`path::test_name`) the same as plain ones; before, such an acceptance criterion was reported as having no known test.
  • The comment ghp done posts says when the ticks it counted are not in the ledger file at the merge commit it links, and the plan warns before the yes. Note for upgraders: this changes the done plan, so a done plan approved under 0.1.0 is refused after upgrading; show it again with ghp done <n> and approve it again.
  • The push preview lists the lines of tasks.md that look like a task but are not read as one, with what a task line must look like. What is planned and written does not change.
  • ghp push with a pull request number and no ledger refuses with E_NOT_AN_ISSUE instead of advising a command that then refuses too.
  • When a comment-mode apply is refused, the refusal says how many /approve or /reject comments were set aside and why (for example: by an account that is not an approver, edited, or from a bot), in fixed words, never the comment's text.
  • ghp decisions <n> --resolve without --note no longer writes an empty note field. Lines written the old way still read the same.

Changed:

  • Every ghp setup refusal starts with its error code (error: E_EXISTS: ...), like the other commands.
  • ghp status names E_ORG_PROJECT_UNSUPPORTED for a Project owned by an organisation; before the merge its next step is the merge, not a fetch.
  • ghp status and ghp activate explain an open issue whose card is at Done by both causes: the card was moved to Done without closing the issue, or the issue was reopened.
  • ghp doctor says what is true when GitHub finds no such Project or repository for the sign-in, instead of "GitHub answered HTTP 200 (unexpected)".
  • ghp branch <n> marks a preview made without a title as not final and names ghp dod <n>.
  • The dod_gate refusal no longer names a release: it says the key was renamed to gate.
  • The reusable gate workflow names the blocking rule ids in the job log, and its strict check also runs when the gate fails. The actions in every workflow are pinned to their Node 24 releases (actions/checkout 5.1.0, actions/setup-python 6.3.0).
  • The ghp-lifecycle workflow's task step, and the review step, end with a short summary instead of a question nobody can answer before the next gate.
  • The plan command no longer forbids ghp approvals check, a read that never approves.
  • Docs: on Spec Kit 1.4.0 with Claude Code the slash commands are named with hyphens (/speckit-ghp-pull 12); the repository setting a workflow needs to open a pull request ("Allow GitHub Actions to create and approve pull requests"); only a comment that starts with the request marker makes a step wait; ghp done waits about 30 seconds plus the reads (about 35 seconds in the live runs); a git fetch between the done preview and the apply changes the plan. The bundle page says the release exists.

Development:

  • The live test suite reads every page of its test issues, follows the Project's closing switches, and can target another repository of the owner's account (GHP_LIVE_REPO).

v0.1.0

Choose a tag to compare

@praveenlavu praveenlavu released this 12 Nov 22:28

First release. See CHANGELOG.md for what is in it.