Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#1,625 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR（30日）
570

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

QueryaHub/Querya-Desktop のほかの issue

QueryaHub/Querya-Desktop の issue をすべて見る

似ている issue

Dart の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。