Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

extension authors: adopt --strict, publish the action, verify the Release hooks (after #1487)

未關閉
  • 哪裡不對？
#1,625 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
20/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
docker, git, github-actions
領域
ci-cd, devops, release

研究方向

Start with docs/extension-registry.md and the linked work in #1487 and #1621. This issue spans release hooks, extension-template and registry workflows, action publishing, and a Codespaces or other-host check of Docker-in-Docker; several steps depend on a release and external organization settings. Done means completing the applicable checklist, verifying the release and template runs, and updating hosts.json when the version should become permanent.

由索引模型根據 Issue 內容生成。

描述

enhancement

Left over from #1487. Everything here waits for the first release that contains the new tester and the Release hooks (they reach main with the next dev → main merge).

After that release
  • Release hooks: the run after the Release workflow logged told QueryaHub/extensions and told QueryaHub/extension-template (secret QUERYA_DISPATCH_TOKEN is set). A manual Run workflow with an already published version does the same check. In the registry a Publish run by repository_dispatch appears and compat.json gets a column for the version.
  • Template follow-up: QueryaHub/extension-template pushed querya-<version> and opened a pull request (or an issue, if the organization still forbids Actions to open pull requests). Merge it, and check that the Test run on the branch is green.
  • --strict is in the tester (#1621). In QueryaHub/extension-template replace the "Fail if the plugin ran without the sandbox" JUnit grep with strict: "true" of the action, and the same in QueryaHub/extensions (.github/actions/test-record).
  • Publish QueryaHub/action-test-extension@v1 (a copy of .github/actions/test-extension, now with strict), then point the template and the registry at it instead of QueryaHub/Querya-Desktop/.github/actions/test-extension@<sha>.
  • Raise hosts.json in QueryaHub/extensions when the new version should become a permanent column of compat.json.
Not done and not blocked by a release
  • devcontainer up on the template, with Docker-in-Docker and the compose file, ending in a green querya-ext-tester ./dist --connect ... --sandbox, was only checked in parts (the Feature installs and the tester passes in the container; the nested Docker daemon did not start on a host without the iptables nat table). Check it in Codespaces or on another host.
  • Optional: let GitHub Actions open pull requests in the organization (Settings → Actions → General), so the template's release pull request is not an issue.
  • Optional: replace the personal access token behind QUERYA_DISPATCH_TOKEN with a GitHub App token, so the hooks do not stop when the person or the token expires.

See docs/extension-registry.md.

主要語言
Dart
星號
23
分支
1
平均合併
31 分鐘
30 天內合併 PR
570

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

QueryaHub/Querya-Desktop 的其他 Issue

查看 QueryaHub/Querya-Desktop 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。