docs: record external-listing submission PRs and their status#1386
Conversation
Add a 提出状況 tracking table to external-listings.md capturing the submitted PRs (awesome-actions #829, awesome-code-review #131, awesome-ai-devtools #697) and their current merge-pending state, plus the live awesome-codex-plugins listing. Annotate the priority list with submission status and fold the redundant codex-plugins note into the table. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No changes to review compared to main. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the external listings documentation (docs/growth/external-listings.md) by adding a tracking table to monitor the submission status of various awesome lists and updating the priority list with current statuses. The reviewer suggested replacing shorthand PR references (e.g., #829) with full markdown links to prevent incorrect auto-linking to the local repository.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| 2. **awesome-actions**—GitHub Action として直球で適合。⏳ 提出済み・マージ待ち（#829） | ||
| 3. **awesome-code-review**—ドメイン一致。非宣伝的な説明文を用意。⏳ 提出済み・マージ待ち（#131） | ||
| 4. **awesome-ai-devtools**—PR & Code Review Bots カテゴリ。⏳ 提出済み・マージ待ち（#697） |
There was a problem hiding this comment.
On GitHub, shorthand references like #829, #131, and #697 will automatically resolve to issues or pull requests within the current repository (s977043/river-review) rather than the external target repositories.
To prevent incorrect auto-linking and provide direct navigation for readers, please use full markdown links matching the tracking table below.
| 2. **awesome-actions**—GitHub Action として直球で適合。⏳ 提出済み・マージ待ち（#829） | |
| 3. **awesome-code-review**—ドメイン一致。非宣伝的な説明文を用意。⏳ 提出済み・マージ待ち（#131） | |
| 4. **awesome-ai-devtools**—PR & Code Review Bots カテゴリ。⏳ 提出済み・マージ待ち（#697） | |
| 2. **awesome-actions**—GitHub Action として直球で適合。⏳ 提出済み・マージ待ち（[#829](https://github.com/sdras/awesome-actions/pull/829)） | |
| 3. **awesome-code-review**—ドメイン一致。非宣伝的な説明文を用意。⏳ 提出済み・マージ待ち（[#131](https://github.com/joho/awesome-code-review/pull/131)） | |
| 4. **awesome-ai-devtools**—PR & Code Review Bots カテゴリ。⏳ 提出済み・マージ待ち（[#697](https://github.com/jamesmurdza/awesome-ai-devtools/pull/697)） |
PlanGate Review
PlanGate review decision: pass
ポリシー: critical=fail / major=fail-if-required (warn) / minor=comment-only / info=skipped — spec: |
What
Add a 提出状況（トラッキング） table to
docs/growth/external-listings.mdrecording which external-listing PRs have been submitted and their current state:mainAlso annotate the 申請優先順位 list with submission status and fold the previously standalone awesome-codex-plugins note into the table.
Why
The doc only recorded the awesome-codex-plugins submission; the other three PRs (submitted 2026-06-24) were not tracked in-repo, so their status was invisible. This makes the submission state auditable from the repo.
Verification
prettier --check/fix-dashes --check/markdownlint: passUNSTABLEstate investigated: no fixable CI failure (empty status rollup, mergeable); it reflects an upstream-side benign state, so no action needed on our entry🤖 Generated with Claude Code