Commit
·
1cd24f0
1
Parent(s):
34e00a7
fixes on analyzer prompt
Browse files- config/constants.py +20 -6
config/constants.py
CHANGED
|
@@ -206,6 +206,10 @@ You are a meticulous GitHub issue analyst. Your task is to analyze all provided
|
|
| 206 |
3. **RECENT RELEASE NOTES:**
|
| 207 |
{release_notes_summary}
|
| 208 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 209 |
**YOUR TASK: Follow this decision tree precisely.**
|
| 210 |
|
| 211 |
**Step 1: Analyze PRs against ALL reported problems.**
|
|
@@ -216,10 +220,18 @@ You are a meticulous GitHub issue analyst. Your task is to analyze all provided
|
|
| 216 |
- After identifying a relevant merged PR, scan the "Release Notes" to see if that exact PR number is mentioned.
|
| 217 |
|
| 218 |
**Step 3: Determine the Verdict.**
|
| 219 |
-
-
|
| 220 |
-
-
|
| 221 |
-
|
| 222 |
-
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 223 |
|
| 224 |
**Step 4: Formulate your response.**
|
| 225 |
|
|
@@ -251,8 +263,10 @@ Then, provide the final report inside `<answer>` tags using the EXACT Markdown s
|
|
| 251 |
- The feature request for a vertical title.
|
| 252 |
|
| 253 |
## Recommendation
|
| 254 |
-
(Base this on the Verdict, Gaps, and the issue's Current State.)
|
| 255 |
-
|
|
|
|
|
|
|
| 256 |
</answer>
|
| 257 |
"""
|
| 258 |
|
|
|
|
| 206 |
3. **RECENT RELEASE NOTES:**
|
| 207 |
{release_notes_summary}
|
| 208 |
|
| 209 |
+
**CRITICAL RULE:**
|
| 210 |
+
- Trust the **ISSUE DETAILS** provided in the context above all else.
|
| 211 |
+
- If the context says `State: open`, the issue IS OPEN. Do not assume it is closed.
|
| 212 |
+
|
| 213 |
**YOUR TASK: Follow this decision tree precisely.**
|
| 214 |
|
| 215 |
**Step 1: Analyze PRs against ALL reported problems.**
|
|
|
|
| 220 |
- After identifying a relevant merged PR, scan the "Release Notes" to see if that exact PR number is mentioned.
|
| 221 |
|
| 222 |
**Step 3: Determine the Verdict.**
|
| 223 |
+
- **Check the Context State (`{issue_state}`) First:**
|
| 224 |
+
- If the context says `open`, the issue IS OPEN. Do not hallucinate that it is closed.
|
| 225 |
+
|
| 226 |
+
- **Verdict Definitions:**
|
| 227 |
+
- `✅ Resolved`:
|
| 228 |
+
- If Issue is **Open**: A merged PR definitively fixes the problem. (Action: Needs Closing).
|
| 229 |
+
- If Issue is **Closed**: The closure confirms the fix.
|
| 230 |
+
- `⚠️ Possibly Resolved`:
|
| 231 |
+
- A PR was merged but it's unclear if it fixes everything.
|
| 232 |
+
- OR the issue is Closed but the resolution is ambiguous.
|
| 233 |
+
- `🚧 In Progress`: Issue is Open and has an open/linked PR.
|
| 234 |
+
- `❌ Unresolved`: Issue is Open with no merged fixes. OR Issue is Closed as "not planned".
|
| 235 |
|
| 236 |
**Step 4: Formulate your response.**
|
| 237 |
|
|
|
|
| 263 |
- The feature request for a vertical title.
|
| 264 |
|
| 265 |
## Recommendation
|
| 266 |
+
(Base this on the Verdict, Gaps, and the issue's Current State: {issue_state}.)
|
| 267 |
+
|
| 268 |
+
*Example (If Open + Resolved):* "This issue is currently **open**, but the fix was merged in PR #10737. It is recommended to **close** this issue."
|
| 269 |
+
*Example (If Closed):* "This issue is already closed and the problem was addressed. No further action is needed."
|
| 270 |
</answer>
|
| 271 |
"""
|
| 272 |
|