Skip to content

chore(catalog): add Jira Integration (Sync Engine) extension#2895

Open
ashbrener wants to merge 4 commits into
github:mainfrom
ashbrener:add-jira-sync-extension
Open

chore(catalog): add Jira Integration (Sync Engine) extension#2895
ashbrener wants to merge 4 commits into
github:mainfrom
ashbrener:add-jira-sync-extension

Conversation

@ashbrener

@ashbrener ashbrener commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Adds a community-catalog listing for spec-kit-jira-sync — an idempotent, drift-aware, fail-closed reconcile engine that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase).

Catalog id is jira-sync (the jira slot is taken by an unrelated extension); display name "Jira Integration (Sync Engine)" disambiguates from the existing "Jira Integration" listing.

Touches the two catalog surfaces:

  1. extensions/catalog.community.json — the new jira-sync entry (field shape matches the sibling linear entry).
  2. docs/community/extensions.md — the table row.

JSON validated. download_url is the GitHub source ZIP at the tag (matches the installer's zipfile.ZipFile extraction). Release: https://github.com/ashbrener/spec-kit-jira-sync/releases/tag/v0.2.0 · License: MIT.

Adds a new community-catalog listing for `spec-kit-jira-sync`
(ashbrener/spec-kit-jira-sync), a reconcile-engine bridge that mirrors
spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per
phase): idempotent, drift-aware, fail-closed.

Catalog id is `jira-sync` because the `jira` id is already taken by an
unrelated extension; display name "Jira Integration (Sync Engine)"
disambiguates from the existing "Jira Integration" listing.

Touches the two catalog surfaces:
1. extensions/catalog.community.json - the new "jira-sync" entry,
   inserted after the existing "jira" entry. Field shape matches the
   sibling "linear" entry exactly.
2. docs/community/extensions.md - the table row, after the existing
   Jira Integration row.

JSON validated; diff is the single entry + the one table row.
Copilot AI review requested due to automatic review settings June 8, 2026 13:02
@ashbrener ashbrener requested a review from mnriem as a code owner June 8, 2026 13:02

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new community extension entry for a Jira sync/reconcile engine and documents it in the community extensions list.

Changes:

  • Added jira-sync metadata to the community extensions catalog
  • Added Jira Integration (Sync Engine) to the community extensions documentation table

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
extensions/catalog.community.json Registers the new jira-sync extension (metadata, links, tags, requirements).
docs/community/extensions.md Lists the new extension in the community extensions table for discoverability.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread extensions/catalog.community.json Outdated
Comment thread docs/community/extensions.md Outdated
…opilot review)

Drop the comparative/absolute framing ('A real …', 'never corrupts your board')
flagged by Copilot; keep the factual, tested capability descriptors (idempotent,
drift-aware, fail-closed). Applies to both the catalog entry and the docs table row.
@ashbrener

ashbrener commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

Thanks @copilot — addressed both comments in 279e692: rewrote the catalog entry and the docs table row to a neutral, capability-focused description, dropping the comparative/absolute framing ("A real …", "never corrupts your board") and keeping only the factual, tested behavior (idempotent, drift-aware, fail-closed). JSON still validates.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0 new

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 2

Comment on lines +1223 to +1225
"version": "0.2.0",
"download_url": "https://github.com/ashbrener/spec-kit-jira-sync/archive/refs/tags/v0.2.0.tar.gz",
"repository": "https://github.com/ashbrener/spec-kit-jira-sync",
Comment thread extensions/catalog.community.json Outdated
Comment on lines +1222 to +1224
"author": "Ash Brener",
"version": "0.2.0",
"download_url": "https://github.com/ashbrener/spec-kit-jira-sync/archive/refs/tags/v0.2.0.tar.gz",
…P-only)

The spec-kit extension installer saves {id}-{version}.zip and extracts via
zipfile.ZipFile (src/specify_cli/extensions.py) — a .tar.gz asset downloads but
fails extraction. Matches every other catalog entry's /archive/refs/tags/vX.zip
convention. Addresses the Copilot review on PR github#2895.
@ashbrener

ashbrener commented Jun 9, 2026

Copy link
Copy Markdown
Contributor Author

Thanks @copilot — both addressed:

  1. download_url .tar.gz.zip (commit on this branch). Confirmed the installer is ZIP-only (src/specify_cli/extensions.py saves {id}-{version}.zip and extracts via zipfile.ZipFile), and this now matches every other catalog entry's /archive/refs/tags/vX.Y.Z.zip convention. GitHub serves a valid ZIP at the tag (HTTP 200).
  2. Version alignment — the PR description now references v0.2.0 (matching the catalog entry and download URL); also dropped the earlier comparative phrasing for a neutral, capability-focused summary.

JSON re-validated. Ready for review.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

  • Files reviewed: 2/2 changed files
  • Comments generated: 0 new

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants