anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Sisyphus ignores project-specific PR templates #8663

New Issue
Closed
opened 2026-02-16 18:10:31 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:10:31 -05:00
Owner
Copy Link
Copy Source

Originally created by @scarf005 on GitHub (Feb 5, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

When creating PRs, the bash tool includes a hardcoded example format (## Summary) that agents blindly follow, ignoring project-specific PR templates stored in .github/pull_request_template.md or other standard locations.

Expected Behavior

Agents should:

  1. Search for PR templates in the repository (e.g., .github/pull_request_template.md, PULL_REQUEST_TEMPLATE.md)
  2. Follow the template structure when it exists
  3. Use a consistent fallback format only when no template is found

Current Behavior

Agents use the hardcoded example format from the bash tool instructions, regardless of whether a project-specific template exists.

Proposed Solution

  1. Use Glob tool to flexibly discover template files in standard locations
  2. Read and follow template structure if found
  3. Provide explicit fallback format for projects without templates
  4. Remove misleading hardcoded examples

Related

  • Part of improving agent adherence to project conventions
  • Affects PR quality and maintainer experience
Originally created by @scarf005 on GitHub (Feb 5, 2026). Originally assigned to: @thdxr on GitHub. ## Problem When creating PRs, the bash tool includes a hardcoded example format (`## Summary`) that agents blindly follow, ignoring project-specific PR templates stored in `.github/pull_request_template.md` or other standard locations. ## Expected Behavior Agents should: 1. Search for PR templates in the repository (e.g., `.github/pull_request_template.md`, `PULL_REQUEST_TEMPLATE.md`) 2. Follow the template structure when it exists 3. Use a consistent fallback format only when no template is found ## Current Behavior Agents use the hardcoded example format from the bash tool instructions, regardless of whether a project-specific template exists. ## Proposed Solution 1. Use Glob tool to flexibly discover template files in standard locations 2. Read and follow template structure if found 3. Provide explicit fallback format for projects without templates 4. Remove misleading hardcoded examples ## Related - Part of improving agent adherence to project conventions - Affects PR quality and maintainer experience
yindo closed this issue 2026-02-16 18:10:31 -05:00
yindo commented 2026-02-16 18:10:31 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #12397: fix: require PR template check before creating PRs - directly addresses the same problem with similar proposed solutions
  • #10640: [FEATURE]: Intercept known Bash tool call patterns and replace them with specialized tools - related to the broader issue of bash tool hardcoding

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 5, 2026): This issue might be a duplicate of existing issues. Please check: - #12397: fix: require PR template check before creating PRs - directly addresses the same problem with similar proposed solutions - #10640: [FEATURE]: Intercept known Bash tool call patterns and replace them with specialized tools - related to the broader issue of bash tool hardcoding Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8663
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?