Repository navigation
Update extension to current spec-kit and glab formats (v1.1.0) - #3
Merged
Merged
Conversation
Bring the extension in line with spec-kit 1.3 and glab 1.128:
- Use the standard `scripts: {sh, ps}` frontmatter with `{SCRIPT}`; the
custom keys and `{SCRIPT:name}` placeholders made registration fail
- Resolve the feature directory with check-prerequisites --paths-only
- Reference commands with __SPECKIT_COMMAND_*__ tokens
- Parse the spec-kit tasks.md ([P] = parallel, [X] = done) and spec.md
(User Story N - Title (Priority: PN)) formats, keeping legacy formats
- Replace glab calls that don't exist (issue create --type, issue
relation, issue list --state, api --repo) with supported flags and
REST API calls, with pagination and --hostname for self-hosted GitLab
- Fix invalid YAML in the mapping file and make local config overrides
apply per key
- Add an optional after_implement hook, task_issue_type option, offline
tests, CI, .extensionignore and a CHANGELOG
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FU4A2CPkCPyvBLkPvUsoVg
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FU4A2CPkCPyvBLkPvUsoVg
Pushing a vX.Y.Z tag now builds spec-kit-gitlab.zip (manifest at the archive root), checks the tag against extension.yml, CHANGELOG.md and README.md, runs the tests and publishes a GitHub release with the zip, its SHA-256 and the install command. The README leads with that single-command install. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FU4A2CPkCPyvBLkPvUsoVg
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the extension in line with spec-kit 1.3.1 and glab 1.128. Several parts of 1.0.0 couldn't work with either one. It also adds a release workflow, so the extension can be installed with a single command.
Breaking issues fixed
gitlab-helpers.sh: ...) with{SCRIPT:name}placeholders. The current registrar only acceptssh/ps/pyand raises "No runnable script variant", and it never replaces{SCRIPT:...}. All commands now usescripts: {sh, ps}→check-prerequisites --json --paths-onlyand{SCRIPT}, and source the helpers from.specify/extensions/gitlab/scripts/bash/.issue create --type,issue relation add,issue list --state all,api ... --repo. They are replaced by the supported equivalents:--linked-issues, the issue links API, a paginated issues API call, andglab api --hostnamewith the URL-encoded project path. The task type is set throughPUT issues/:iid issue_type=task.tasks.md,[P]marks a parallel task (it isn't a priority), andimplementchecks tasks off as[X]. Stories inspec.mdare### User Story 1 - Title (Priority: P1). Both are parsed now, the old formats still work, and tasks inherit their story's priority.stories: {}produced invalid YAML.__SPECKIT_COMMAND_*__tokens, so they render for both slash-command and skills agents./speckit.specdoesn't exist and is replaced by the specify command.Simpler install
release.yml: pushing avX.Y.Ztag checks the tag againstextension.yml,CHANGELOG.mdand the README install command, then runs the tests and buildsspec-kit-gitlab.zipwithextension.ymlat the archive root. It publishes a GitHub release with the zip, its SHA-256 and the install command.specify extension add gitlab --from https://github.com/ohartwig/spec-kit-gitlab/releases/download/v1.1.0/spec-kit-gitlab.zipreleases/download/<tag>/<asset>.zip).Other changes
requires.speckit_version: ">=0.12.17", glab>=1.50.0, and jq listed as a required tool. Addedrepository,homepage,categoryandeffect.after_implementhook that offers to run close-issues, plus amapping.task_issue_typeoption (taskorissue).${...}placeholders, because spec-kit copies it into the project on install and doesn't expand them.set -euo pipefailin the caller's shell. The YAML parsing works with BSD/macOS sed and with bash 3.2.--dry-runto close-issues and sync, and--no-updateto status.tests/test-helpers.sh), a CI workflow (tests on Ubuntu and macOS, plus ShellCheck),.extensionignoreandCHANGELOG.md.Testing
bash tests/test-helpers.sh: 36 checks pass, under the default locale andLC_ALL=C.specifyCLI, running against a live GitLab instance, and thegh release createstep (it runs only when a tag is pushed).🤖 Generated with Claude Code
https://claude.ai/code/session_01FU4A2CPkCPyvBLkPvUsoVg