fix(issue-sync): issues イベント自動トリガーを無効化(PR作成権限制限対応) - #87
Conversation
GitHub Actions の PR 作成権限制限 (createPullRequest not permitted) により issue イベント自動トリガーが毎回失敗し CI パネルにノイズが発生していた。 Issues は GitHub Issues で直接管理済み。TASKS.md 同期が必要な場合は workflow_dispatch で手動実行する。 Closes #85 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughGitHub issue イベント(opened/closed/reopened など)での自動実行トリガーを削除し、 Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR disables the issues event trigger for the “Issue Sync” GitHub Actions workflow to stop it from running (and failing) on every issue event due to repository settings that prevent GitHub Actions from creating/approving PRs. The workflow is left as workflow_dispatch-only so it can be run manually when needed.
Changes:
- Removed the
issuesevent trigger from the Issue Sync workflow. - Added inline comments explaining why automatic triggering was disabled and that it should be run manually instead.
| # Auto-trigger on issue events disabled: GitHub Actions cannot create or approve PRs in this repo. | ||
| # Issues are tracked directly in GitHub Issues. Run manually via workflow_dispatch only if needed. |
There was a problem hiding this comment.
The new header comment (and PR description) suggests TASKS.md can still be updated via workflow_dispatch, but the workflow still relies on gh pr create/gh pr merge using secrets.GITHUB_TOKEN. With “Allow GitHub Actions to create and approve pull requests” disabled, manual dispatch will fail the same way. Please either (a) document that a PAT (e.g., secrets.GH_PAT) is required for manual runs, or (b) adjust the workflow to skip PR creation/merge when PR creation is disabled (or switch to an alternate update mechanism).
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/issue-sync.yml (1)
65-65:⚠️ Potential issue | 🟡 MinorPR 本文テキストが不正確です
PR 本文に「issue event で トリガーされた」と記載されていますが、ワークフローは現在
workflow_dispatch(手動実行)のみに変更されており、issue イベントではトリガーされません。📝 修正案
- --body "Automated TASKS.md sync triggered by issue event. Merges automatically after CI passes." ` + --body "Automated TASKS.md sync triggered manually via workflow_dispatch. Merges automatically after CI passes." `または、より簡潔に:
- --body "Automated TASKS.md sync triggered by issue event. Merges automatically after CI passes." ` + --body "Automated TASKS.md sync from GitHub Issues. Merges automatically after CI passes." `🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/issue-sync.yml at line 65, PR 本文の説明が実際のトリガーと不一致しています: locate the string --body "Automated TASKS.md sync triggered by issue event. Merges automatically after CI passes." and update the message to accurately reflect the workflow trigger (e.g. "Automated TASKS.md sync triggered manually via workflow_dispatch. Merges automatically after CI passes." or a shorter variant like "Automated TASKS.md sync (manual run). Merges after CI passes."). Ensure the updated --body text replaces the incorrect "issue event" wording so the commit/PR message matches the current manual workflow_trigger.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/issue-sync.yml:
- Around line 4-6: README.md と CHANGELOG.md
に記載されている「自動同期/イベントトリガー自動同期」という表現が現在のワークフロー (.github/workflows/issue-sync.yml) が
workflow_dispatch のみで手動実行に限定されている状態と齟齬があるため、該当箇所を手動実行のみを示す文言に更新してください(README.md
の該当行で "issue-sync.yml 自動同期" を「手動実行 (workflow_dispatch) のみ」などに、CHANGELOG.md の該当行で
"Issue イベントトリガー自動同期" を同様に「手動実行に変更」などに置き換え、必要ならワークフローの意図を簡潔に説明する一文を追加してください)。
---
Outside diff comments:
In @.github/workflows/issue-sync.yml:
- Line 65: PR 本文の説明が実際のトリガーと不一致しています: locate the string --body "Automated
TASKS.md sync triggered by issue event. Merges automatically after CI passes."
and update the message to accurately reflect the workflow trigger (e.g.
"Automated TASKS.md sync triggered manually via workflow_dispatch. Merges
automatically after CI passes." or a shorter variant like "Automated TASKS.md
sync (manual run). Merges after CI passes."). Ensure the updated --body text
replaces the incorrect "issue event" wording so the commit/PR message matches
the current manual workflow_trigger.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ddb1016c-a2c1-4dbd-9209-f503d2db2744
📒 Files selected for processing (1)
.github/workflows/issue-sync.yml
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Agent
- GitHub Check: test-and-validate
🧰 Additional context used
📓 Path-based instructions (4)
{Makefile,**.{sh,bash},**.yml,**.yaml,.github/workflows/**,.gitlab-ci.yml,.circleci/**}
📄 CodeRabbit inference engine (AGENTS.md)
Do not use success faking patterns (e.g., || true) in CI/build commands; treat all CI failures as actual failures requiring genuine fixes
Files:
.github/workflows/issue-sync.yml
{test/**,**.test.{js,ts,tsx},**.spec.{js,ts,tsx},.eslintrc*,tsconfig.json,**/.github/workflows/**,**.yml,**.yaml}
📄 CodeRabbit inference engine (AGENTS.md)
Implement STABLE judgment criteria: all of install, lint, test, build, and CI must pass with zero errors and zero security issues
Files:
.github/workflows/issue-sync.yml
{.github/workflows/**,.gitlab-ci.yml,.circleci/**,**.yml,**.yaml}
📄 CodeRabbit inference engine (AGENTS.md)
Limit CI Manager retries to maximum 15 attempts; mark task as Blocked after encountering the same error 3 times
Files:
.github/workflows/issue-sync.yml
.github/workflows/**/*.{yml,yaml}
📄 CodeRabbit inference engine (CLAUDE.md)
.github/workflows/**/*.{yml,yaml}: Add lint success to CI quality gate
Add unit test success to CI quality gate
Add build success to CI quality gate
Add dependency and security scan to CI quality gate
Files:
.github/workflows/issue-sync.yml
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
Repo: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-14T03:27:19.454Z
Learning: Respond to GitHub / CI / Issues in Japanese for communication and explanations
Learnt from: CR
Repo: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New PR: 0
File: docs/codex/AGENTS.md:0-0
Timestamp: 2026-04-14T02:13:12.468Z
Learning: Do not push directly to `main` branch; use PR-based workflow
Learnt from: CR
Repo: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-14T03:27:19.454Z
Learning: Require PR before merging to main
Learnt from: CR
Repo: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New PR: 0
File: Claude/CLAUDE.md:0-0
Timestamp: 2026-04-14T02:12:21.915Z
Learning: main branch direct push is prohibited; branch or WorkTree is required, and PR is mandatory with CI success before merge
📚 Learning: 2026-04-14T02:12:54.820Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-14T02:12:54.820Z
Learning: Use Issue-driven development workflow where all work is tracked through Issues before implementation begins
Applied to files:
.github/workflows/issue-sync.yml
📚 Learning: 2026-04-14T03:27:19.454Z
Learnt from: CR
Repo: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-14T03:27:19.454Z
Learning: Set up GitHub Projects with state transitions: Inbox → Backlog → Ready → Design → Development → Verify → Deploy Gate → Done/Blocked
Applied to files:
.github/workflows/issue-sync.yml
🔇 Additional comments (1)
.github/workflows/issue-sync.yml (1)
4-5: 明確な説明コメントで LGTM!手動トリガーのみに変更した理由と使用方法が明確に説明されています。リポジトリ設定による制約と手動実行の必要性が適切にドキュメント化されています。
| # Auto-trigger on issue events disabled: GitHub Actions cannot create or approve PRs in this repo. | ||
| # Issues are tracked directly in GitHub Issues. Run manually via workflow_dispatch only if needed. | ||
| workflow_dispatch: |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check documentation files for outdated "automatic sync" references
# Search for automatic sync references in README and CHANGELOG
echo "=== Checking README.md for automatic sync references ==="
rg -n "issue-sync.*自動" README.md || echo "No matches found in README.md"
echo -e "\n=== Checking CHANGELOG.md for automatic sync references ==="
rg -n "issue-sync.*自動|Issue.*イベントトリガー" CHANGELOG.md || echo "No matches found in CHANGELOG.md"
echo -e "\n=== Checking for other references to issue-sync workflow ==="
rg -n "issue-sync" --type md -g '!.github/**' | head -20Repository: Kensan196948G/ClaudeCLI-CodexCLI-CopilotCLI-StartUpTools-New
Length of output: 618
README.md と CHANGELOG.md のドキュメント更新が必要
README.md:48 と CHANGELOG.md:52 に「自動同期」「イベントトリガー自動同期」と記載されていますが、ワークフローは workflow_dispatch のみの手動実行に変更されています。ドキュメントを現在の動作に合わせて更新してください。
- README.md:48: "issue-sync.yml 自動同期" → 手動実行のみに更新
- CHANGELOG.md:52: "Issue イベントトリガー自動同期" → 手動実行のみに更新
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/workflows/issue-sync.yml around lines 4 - 6, README.md と
CHANGELOG.md に記載されている「自動同期/イベントトリガー自動同期」という表現が現在のワークフロー
(.github/workflows/issue-sync.yml) が workflow_dispatch
のみで手動実行に限定されている状態と齟齬があるため、該当箇所を手動実行のみを示す文言に更新してください(README.md の該当行で
"issue-sync.yml 自動同期" を「手動実行 (workflow_dispatch) のみ」などに、CHANGELOG.md の該当行で
"Issue イベントトリガー自動同期" を同様に「手動実行に変更」などに置き換え、必要ならワークフローの意図を簡潔に説明する一文を追加してください)。
v2.9.0 セクションを `[v2.9.0-dev] - 2026-04-08` から `[v2.9.0] - 2026-04-14 (STABLE)` に更新し、 ClaudeOS v7.5 の全成果 (Boot Sequence Step 3/7/9 完全実装、CodeRabbit 統合、 /team-onboarding、ループ時間最適化、Issue Sync 修正) を反映。 新規に `[v3.0.0] - Unreleased` セクションを追加し、Phase 4 残タスク (セキュリティ監査 / E2E テスト / リリースタグ) と Go/No-Go 基準を明文化。 - テスト数: 304 → 311 件に更新 - 追加 PR: #77, #79, #80, #81, #82, #83, #84, #86, #87, #88, #89 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
v2.9.0 セクションを `[v2.9.0-dev] - 2026-04-08` から `[v2.9.0] - 2026-04-14 (STABLE)` に更新し、 ClaudeOS v7.5 の全成果 (Boot Sequence Step 3/7/9 完全実装、CodeRabbit 統合、 /team-onboarding、ループ時間最適化、Issue Sync 修正) を反映。 新規に `[v3.0.0] - Unreleased` セクションを追加し、Phase 4 残タスク (セキュリティ監査 / E2E テスト / リリースタグ) と Go/No-Go 基準を明文化。 - テスト数: 304 → 311 件に更新 - 追加 PR: #77, #79, #80, #81, #82, #83, #84, #86, #87, #88, #89 Co-authored-by: 有藤 健太郎 <k-aritoh@mirai-const.co.jp> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
issuesイベントで毎回起動し、gh pr createが失敗し続けていたissuesトリガーを削除しworkflow_dispatch(手動)のみに変更Why not enable Actions PR creation?
リポジトリ設定変更はコード変更では対応不可。また TASKS.md の内容は
GitHub Issues の情報と完全に重複しており、Issues が主管理ツールとして確立済み。
自動 CI ノイズを排除し、必要時のみ手動実行する方式が最適と判断。
Impact
issueイベント発火時のIssue Syncワークフロー: 不実行(ノイズ排除)workflow_dispatchで引き続き可能Test plan
Closes #85
🤖 Generated with Claude Code
Summary by CodeRabbit