ci: add release-please kick workflow + script (W1+W5)#900
Merged
Conversation
PR 3/3 of P0 retrospective follow-up (docs/development/retrospectives/2026-05-21-25.md). Adds workflow_dispatch + local script to advance the release-please branch by an empty commit when required status checks fail to register on the auto-generated branch. Codifies the pattern previously kept only in AGENT_LEARNINGS.md and applied manually 4 times during the v0.51.0-v0.55.0 sprint. Preferred path: Actions UI workflow_dispatch. Fallback: scripts/release-please-kick.sh (works during fs-loss).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
River Reviewer
選択されたスキル (0)
スキップされたスキル (87)
優先度サマリー
スコア (参考値)結果(スコア): 96/100 内訳:
指摘
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Comment on lines
+9
to
+11
| ## Preferred: `workflow_dispatch` | ||
|
|
||
| 1. Go to **Actions → Release Please Kick → Run workflow**. |
Contributor
There was a problem hiding this comment.
PRのタイトルと説明には workflow_dispatch ワークフローの追加が含まれていますが、.github/workflows/release-please-kick.yml ファイルがこのPRの差分に含まれていないようです。このままでは「Preferred」として記載されている手順が実行できません。意図的に別PRに分けている場合は、その旨を説明に追記するか、ドキュメントの記述を調整することを検討してください。
References
- リポジトリのポリシー（GEMINI.md 9行目）に従い、出力は日本語を基準としています。 (link)
|
|
||
| 1. Go to **Actions → Release Please Kick → Run workflow**. | ||
| 2. Leave `branch` as the default | ||
| (`release-please--branches--main--components--river-reviewer`) unless the |
Contributor
There was a problem hiding this comment.
release-please-config.json の設定（component: ""）に基づくと、デフォルトのブランチ名は release-please--branches--main になるはずです。ドキュメント内の例示を現在の設定に合わせるか、より汎用的な記述にすることを検討してください。
Suggested change
| (`release-please--branches--main--components--river-reviewer`) unless the | |
| (`release-please--branches--main`) unless the |
| set -euo pipefail | ||
|
|
||
| REPO="${REPO:-$(gh repo view --json nameWithOwner --jq .nameWithOwner)}" | ||
| BRANCH="${1:-release-please--branches--main--components--river-reviewer}" |
Contributor
There was a problem hiding this comment.
release-please-config.json の設定では component が空文字（""）になっています。この場合、release-please が作成するブランチ名は通常 release-please--branches--main となります。現在のデフォルト値 ...--components--river-reviewer はこの設定と不一致があるため、デフォルトのまま実行するとエラーになる可能性があります。リポジトリ全体の構成に合わせてデフォルト値を調整することを検討してください。
Suggested change
| BRANCH="${1:-release-please--branches--main--components--river-reviewer}" | |
| BRANCH="${1:-release-please--branches--main}" |
Contributor
PlanGate Review
PlanGate review decision: pass
ポリシー: critical=fail / major=fail-if-required (warn) / minor=comment-only / info=skipped — spec: |
4 tasks
s977043
added a commit
that referenced
this pull request
May 25, 2026
#902) Follow-up to multi-perspective review (Self/Codex/Gemini) of PR #898-#900. 3 convergent defects fixed in one PR per Codex's process-hardening grouping. A. release-please-kick.yml: add concurrency guard (group: release-please-kick) - prevents double-click 422 race on PATCH refs B. branch input default: blank → auto-detect via gh pr list - eliminates silent 404 if release-please component changes - applied to both workflow and scripts/release-please-kick.sh C. retrospectives/2026-05-21-25.md: add reopen conditions - 4 explicit triggers (new info / explicit scope / risk down / time+observation) - "対応を自律的に進めて" is re-judgment trigger, not auto-release - allowed-in-Stop list + 3-step release procedure
This was referenced May 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR 3/3 of the P0 retrospective follow-up set (see #898 retrospective doc; companion #899 community-skills registry).
Codifies the release-please kick pattern that was applied 4 times manually during the v0.51.0–v0.55.0 sprint:
Actions → Release Please Kick → Run workflow(workflow_dispatch)scripts/release-please-kick.sh— local CLI using the samegh apiempty-commit pattern (works during fs-loss incidents)docs/runbook/release-please-kick.mdPer Codex's verbatim retrospective guidance: "W1/W5: release-please kick の自動化。統合して 1 件でよい。
workflow_dispatch優先、script は補助。empty commit script だけだと運用の本質が残る"Test plan
node scripts/fix-dashes.mjs --checkclean