π OpenHands: AI-Driven Development
fix(resolver): use literal placeholders in branch/PR naming instructions (#14521)
Alona9979a989510b
diff --git a/openhands/app_server/integrations/templates/resolver/jira/jira_instructions.j2 b/openhands/app_server/integrations/templates/resolver/jira/jira_instructions.j2index 8fe6c11b96..acfdcd99c5 100644--- a/openhands/app_server/integrations/templates/resolver/jira/jira_instructions.j2+++ b/openhands/app_server/integrations/templates/resolver/jira/jira_instructions.j2@@ -5,9 +5,9 @@ Follow these instructions carefully:1. Thoroughly analyze the issue description and Acceptance Criteria before writing any code.2. If requirements are ambiguous or conflicting, request clarification from the user.3. When creating branches and pull requests, adhere strictly to the following naming conventions using the issue key:- * Branch: `{{ issue_key }}-{{ description_in_kebab_case }}`+ * Branch: `<ISSUE-KEY>-<short-description-in-kebab-case>`* Example: `FRE-24-improve-form-validations`- * PR Title: `[{{ issue_key }}] {{ pr_title }}`+ * PR Title: `[<ISSUE-KEY>] <title>`* Example: `[FRE-24] Improve form validations`4. If the repository already contains a style guides and PR templates, respect those.5. Write clean, maintainable code that meets the requirements outlined in the issue.diff --git a/openhands/app_server/integrations/templates/resolver/jira_dc/jira_dc_instructions.j2 b/openhands/app_server/integrations/templates/resolver/jira_dc/jira_dc_instructions.j2index 8fe6c11b96..acfdcd99c5 100644--- a/openhands/app_server/integrations/templates/resolver/jira_dc/jira_dc_instructions.j2+++ b/openhands/app_server/integrations/templates/resolver/jira_dc/jira_dc_instructions.j2@@ -5,9 +5,9 @@ Follow these instructions carefully:1. Thoroughly analyze the issue description and Acceptance Criteria before writing any code.2. If requirements are ambiguous or conflicting, request clarification from the user.3. When creating branches and pull requests, adhere strictly to the following naming conventions using the issue key:- * Branch: `{{ issue_key }}-{{ description_in_kebab_case }}`+ * Branch: `<ISSUE-KEY>-<short-description-in-kebab-case>`* Example: `FRE-24-improve-form-validations`- * PR Title: `[{{ issue_key }}] {{ pr_title }}`+ * PR Title: `[<ISSUE-KEY>] <title>`* Example: `[FRE-24] Improve form validations`4. If the repository already contains a style guides and PR templates, respect those.5. Write clean, maintainable code that meets the requirements outlined in the issue.diff --git a/openhands/app_server/integrations/templates/resolver/linear/linear_instructions.j2 b/openhands/app_server/integrations/templates/resolver/linear/linear_instructions.j2index 8fe6c11b96..acfdcd99c5 100644--- a/openhands/app_server/integrations/templates/resolver/linear/linear_instructions.j2+++ b/openhands/app_server/integrations/templates/resolver/linear/linear_instructions.j2@@ -5,9 +5,9 @@ Follow these instructions carefully:1. Thoroughly analyze the issue description and Acceptance Criteria before writing any code.2. If requirements are ambiguous or conflicting, request clarification from the user.3. When creating branches and pull requests, adhere strictly to the following naming conventions using the issue key:- * Branch: `{{ issue_key }}-{{ description_in_kebab_case }}`+ * Branch: `<ISSUE-KEY>-<short-description-in-kebab-case>`* Example: `FRE-24-improve-form-validations`- * PR Title: `[{{ issue_key }}] {{ pr_title }}`+ * PR Title: `[<ISSUE-KEY>] <title>`* Example: `[FRE-24] Improve form validations`4. If the repository already contains a style guides and PR templates, respect those.5. Write clean, maintainable code that meets the requirements outlined in the issue.