From d083df402625ed48e215f780014a3bc49d45f6a8 Mon Sep 17 00:00:00 2001 From: Gunju Kim Date: Fri, 27 Feb 2026 23:22:16 +0000 Subject: [PATCH] Remove PR creation instructions from kelos-self-update TaskSpawner Replace PR creation instructions with issue-only directives in the kelos-self-update TaskSpawner, matching the pattern established in the other non-worker TaskSpawners (kelos-fake-user, kelos-fake-strategist). Non-worker TaskSpawners should only create issues, not PRs, so that maintainers can provide feedback through a consistent workflow. Fixes #465 Co-Authored-By: Claude Opus 4.6 --- self-development/kelos-self-update.yaml | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/self-development/kelos-self-update.yaml b/self-development/kelos-self-update.yaml index 09eabf7..d59622b 100644 --- a/self-development/kelos-self-update.yaml +++ b/self-development/kelos-self-update.yaml @@ -65,17 +65,11 @@ spec: - Verify that GitHub Actions workflows that reference self-development files are up to date Actions: - - If you find improvements, create a PR: - ``` - git checkout -b kelos-self-update-{{.ID}} - # ... make changes ... - git push -u origin kelos-self-update-{{.ID}} - gh pr create --title "" --body "<description>" --label generated-by-kelos --label ok-to-test - ``` - - If the changes are too large or need discussion, create an issue instead: + - If you find improvements, create a GitHub issue with your findings and proposals: ``` gh issue create --title "<title>" --body "<description>" --label generated-by-kelos --label kelos/needs-input ``` + - Do NOT create PRs. Only create issues Constraints: - Focus on ONE area per run, do it thoroughly