fix(ci): update-flake-lock PR で CI がトリガーされるよう GitHub App トークンを使用#233
Merged
fix(ci): update-flake-lock PR で CI がトリガーされるよう GitHub App トークンを使用#233
Conversation
GITHUB_TOKEN で作成した PR は GitHub の制限により後続 CI がトリガーされない。 nix-update-pr.yaml と同様に GitHub App トークンを使って PR を作成することで、 lint・integration-test・nix 等の CI チェックが正常に動作するようにする。 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
概要
update-flake-lock.yamlがGITHUB_TOKENで PR を作成していたため、GitHub の制限により後続 CI（lint・nix・integration-test）がトリガーされていなかったnix-update-pr.yamlと同様にactions/create-github-app-tokenで GitHub App トークンを生成し、update-flake-lockアクションに渡すよう変更GITHUB_TOKEN向けのpermissions: contents: write / pull-requests: writeは不要になったため削除テスト計画
workflow_dispatchで手動実行し、PR が作成されることを確認🤖 Generated with Claude Code