Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[extension] Update SpecAssay Check extension to v0.5.2

Aperta
#4,718 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
55/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
tooling

Direzione di ricerca

The issue is about updating a community catalog entry for an extension. The main file to edit is likely extensions/catalog.community.json, which had a merge conflict. Follow the manual steps in the issue to download the artifact, resolve the conflict, and push the branch. Check the extension's version, release URL, and SHA-256 in the catalog file. Ensure the changes align with the community extensions documentation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agentic-workflows automated extension-submission

Summary

Update the existing SpecAssay Check community catalog entry from v0.4.12 to v0.5.2, including the new release URL, verified archive SHA-256, expanded command count, and Spec Kit version range. Keep the community extensions documentation aligned.

Validation

All submission checks passed:

  • Issue title, extension ID, and semver validated
  • Repository is public and contains the required README.md, LICENSE, and extensions/specassay-check/extension.yml files
  • Download URL is repository-owned, tag-pinned to v0.5.2, returns HTTP 200, and has a matching GitHub release
  • Submitted SHA-256 matched the downloaded archive: f481c6794d0cffc6d532721c1acc378287ba291b3e74dbe1e54eef083d1e7a20
  • Required testing and submission checklist items are checked
  • Catalog JSON validated successfully

Closes #4711

cc @rdryfoos


[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Original error: ERR_SYSTEM: pushSignedCommits: failed to rebase commit range onto current GraphQL parent (c8476e2682311695f4d267fcf78ac7da2bf19065). Resolve conflicts by rebasing/cherry-picking locally and retry. Root cause: Auto-merging extensions/catalog.community.json CONFLICT (content): Merge conflict in extensions/catalog.community.json Rebasing (1/1) error: could not apply a7b10b36... Update SpecAssay Check extension to v0.5.2 hint: Resolve all conflicts manually, mark them as resolved with hint: "git add/rm (conflicted_files)", then run "git rebase --continue". hint: You can instead skip this commit: run "git rebase --skip". hint: To abort and get back to the state before "git rebase", run "git rebase --abort". hint: Disable this message with "git config set advice.mergeConflict false" Could not apply a7b10b36... # Update SpecAssay Check extension to v0.5.2

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

Create the pull request manually
# Download the artifact from the workflow run
gh run download '35923251938' -n agent -D '/tmp/agent-35923251938'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-35923251938/aw-github-spec-kit-update-specassay-check-extension.bundle'
temp_ref='refs/bundles/create-pr-update-specassay-check-extension-d0bba9bbbc5c219c-3feb9ca5'
target_ref='refs/heads/update-specassay-check-extension-d0bba9bbbc5c219c'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
  bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
  echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
  exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'update-specassay-check-extension-d0bba9bbbc5c219c'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"

# Push the branch to the target remote
git push 'origin' 'update-specassay-check-extension-d0bba9bbbc5c219c'

# Create the pull request
gh pr create --title '[extension] Update SpecAssay Check extension to v0.5.2' --base 'main' --head 'update-specassay-check-extension-d0bba9bbbc5c219c' --repo 'github/spec-kit'

Generated by 🧩 Add Community Extension from Issue Submission for #4711 · copilot · gpt52codex · 3.17 AIC · ⌖ 12.5 AIC · ⊞ 23.9K · ◷

Lingua principale
Python
Stelle
138k
Fork
12.4k
Merge medio
3g 2h
PR unite (30g)
169

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/spec-kit

Tutte le issue di github/spec-kit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.