Skip to content

chore(catalog): align tag issue-tracker -> issue-tracking#27

Merged
ashbrener merged 1 commit into
mainfrom
chore/align-tag-issue-tracking
May 31, 2026
Merged

chore(catalog): align tag issue-tracker -> issue-tracking#27
ashbrener merged 1 commit into
mainfrom
chore/align-tag-issue-tracking

Conversation

@ashbrener

Copy link
Copy Markdown
Owner

What

Aligns the extension.yml tag issue-trackerissue-tracking to match the spec-kit community-catalog taxonomy (the jira and azure-devops catalog entries use issue-tracking; nothing else uses issue-tracker).

Why

Surfaced by Copilot review on the catalog submission (github/spec-kit#2749). Keeping the manifest tag in sync with the catalog entry prevents a future re-sync from regressing the catalog back to the one-off issue-tracker tag.

Note

This one-line change was initially committed straight to main by mistake; that commit has been removed from main and re-routed through this PR for review. Diff is +1 / −1 on extension.yml.

@ashbrener ashbrener merged commit 1bbb6f9 into main May 31, 2026
12 checks passed
@ashbrener ashbrener deleted the chore/align-tag-issue-tracking branch May 31, 2026 05:32
ashbrener added a commit that referenced this pull request May 31, 2026
…anguage) (#30)

extension.yml's header notes its description should match the GitHub repo
description so the catalog entry and README cover read the same way. The
GitHub About field was just rewritten in plain language (#29); this brings
the manifest's catalog-facing description into sync:

  before: Mirror spec-kit feature directories into Linear (filesystem →
          Linear, reconcile-based, unidirectional).
  after:  Automatically mirror your spec-kit specs into Linear — one issue
          per spec, a sub-issue per task phase, kept in sync as you work.

Prose only; the catalog taxonomy lives in tags: (aligned separately in
#27), so this does not affect the community-catalog submission's
classification — only its human-readable blurb.
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.

1 participant