[extension] Update SpecAssay Check extension to v0.5.2
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 55/100
- Issue 類型
- 文件
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 領域
- tooling
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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
agentartifact 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 · ◷
- 主要語言
- Python
- 星號
- 138k
- 分支
- 12.4k
- 平均合併
- 3 天 2 小時
- 30 天內合併 PR
- 169
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/spec-kit 的其他 Issue
-
enhancement needs-triage triage-can-wait
難度 2/5 1-3 小時 新手友好度 65/100
-
preset-submission triage-must-have validation-passed
難度 2/5 1-3 小時 新手友好度 75/100
-
extension-submission triage-must-have validation-passed
難度 2/5 1-3 小時 新手友好度 70/100
-
extension-submission triage-can-wait validation-passed
難度 2/5 1-3 小時 新手友好度 76/100
-
enhancement needs-triage triage-can-wait
難度 2/5 1-3 小時 新手友好度 65/100
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 75/100
stephrobert/dsoxlab#238 ·
-
難度 2/5 1-3 小時 新手友好度 75/100
-
難度 2/5 1-3 小時 新手友好度 75/100
sublimehq/package_control#1780 ·
-
難度 2/5 1-3 小時 新手友好度 65/100
-
難度 2/5 1-3 小時 新手友好度 70/100
nwg-piotr/nwg-displays#145 ·