Skip to content

Remove PR creation instructions from kelos-self-update TaskSpawner #469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gjkim42 merged 1 commit into from
Feb 27, 2026
+2 −8
Merged

Remove PR creation instructions from kelos-self-update TaskSpawner #469

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 2 additions & 8 deletions self-development/kelos-self-update.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 "<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
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 27, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: The README still describes kelos-self-update as creating PRs (line 38: → PR or Issue, line 211: "Creates a PR for code changes or an issue if discussion is needed"). Update both to reflect the new issue-only behavior, matching the pattern of other non-worker TaskSpawners.

(Based on your team's feedback about keeping documentation and config updated with changes.)

View Feedback

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At self-development/kelos-self-update.yaml, line 72:

<comment>The README still describes `kelos-self-update` as creating PRs (line 38: `→ PR or Issue`, line 211: "Creates a PR for code changes or an issue if discussion is needed"). Update both to reflect the new issue-only behavior, matching the pattern of other non-worker TaskSpawners.

(Based on your team's feedback about keeping documentation and config updated with changes.) </comment>

<file context>
@@ -65,17 +65,11 @@ spec:
         ```
         gh issue create --title "<title>" --body "<description>" --label generated-by-kelos --label kelos/needs-input
         ```
+      - Do NOT create PRs. Only create issues
 
       Constraints:
</file context>
Fix with Cubic

Constraints:
- Focus on ONE area per run, do it thoroughly
Expand Down
Loading