You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`TRIAGE_SOURCEGRAPH_TOKEN`: Sourcegraph access token for MCP integration
356
356
-`TRIAGE_SOURCEGRAPH_MCP_URL`: Sourcegraph MCP server URL
357
357
-`TRIAGE_REDIS_URL`: Redis URL for Celery broker and result backend (default: redis://localhost:6379/0)
358
+
-`TRIAGE_DISABLE_ISSUE_CREATION`: Set to "true" to disable GitHub issue creation (logs proposals instead). Useful for local testing without creating real issues
359
+
-`TRIAGE_LOG_LEVEL`: Set to "DEBUG" to enable detailed agent conversation logging (default: INFO)
export TRIAGE_DISABLE_ISSUE_CREATION="false"# Set to "true" for testing without creating issues
125
132
```
126
133
127
134
**Notes**:
128
135
129
136
-`TRIAGE_GITHUB_PRIVATE_KEY` should contain the full PEM content (including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----` lines), not just a file path.
130
137
-`TRIAGE_GITHUB_WEBHOOK_SECRET` should be a secure random string. Generate one with:
138
+
-`TRIAGE_DISABLE_ISSUE_CREATION` when set to `"true"`, disables GitHub issue creation and instead logs the proposal. Useful for local testing and development to avoid cluttering repositories with test issues.
- Failure logs excerpt demonstrating the error condition
31
40
- Workflow file path (if available)
32
41
- Recent commit history"""
33
-
34
42
SYSTEM_PROMPT_MCP_TOOLS="""
35
43
36
44
## Remote Repository Access
37
45
38
-
**All repository code inspection must happen through the Sourcegraph MCP server.** You do not have local access to any files in the repository. Do not assume you can read files directly or that the repository is checked out on your filesystem.
46
+
**CRITICAL: All repository code inspection MUST happen through the Sourcegraph MCP server.** You do not have local access to any files in the repository. Do not assume you can read files directly or that the repository is checked out on your filesystem.
39
47
40
-
You have access to a Sourcegraph MCP server (OAuth-authenticated) providing:
41
-
- Code search (keyword and semantic search across repositories)
42
-
- File reading (sg_read_file) — the ONLY way to read repository files
43
-
- Directory listing (sg_list_files) — the ONLY way to list repository contents
44
-
- Symbol navigation (sg_find_references, sg_go_to_definition)
45
-
- Commit and diff search
48
+
**You MUST use the following Sourcegraph MCP tools for all code investigation:**
46
49
47
-
Use these MCP tools exclusively to investigate the codebase, examine workflow configurations, and analyze recent changes that may have introduced the failure."""
50
+
- **sg_read_file** — Read file contents (the ONLY way to read repository files)
51
+
- **sg_list_files** — List directory contents (the ONLY way to browse the repository)
52
+
- **sg_list_repos** — Verify repository names and access
53
+
- **sg_keyword_search** — Search for exact code patterns, function names, and keywords
54
+
- **sg_nls_search** — Semantic search for concepts and related code
55
+
- **sg_go_to_definition** — Navigate to symbol definitions
56
+
- **sg_find_references** — Find where symbols are used
57
+
- **sg_commit_search** — Search commit history and messages
58
+
- **sg_diff_search** — Search code changes in diffs
59
+
- **sg_compare_revisions** — Compare code between commits
60
+
61
+
**IMPORTANT:** Start your investigation by using sg_list_repos to verify the repository name, then use sg_keyword_search or sg_nls_search to find relevant code, workflow files, and configuration. Use sg_read_file to examine specific files. These tools are OAuth-authenticated and provide full access to the codebase."""
48
62
49
63
SYSTEM_PROMPT_WORKFLOW="""
50
64
@@ -53,11 +67,11 @@
53
67
1. Examine the logs_excerpt to identify the immediate failure symptom
54
68
2. Use available tools to investigate root cause (workflow YAML, recent commits, dependency files, code changes)
55
69
3. Form a hypothesis about the underlying issue
56
-
4. Once you have high confidence in your diagnosis, submit your remediation proposal
70
+
4. REQUIRED: Submit your remediation proposal using the submit_proposal tool
57
71
58
72
## Remediation Proposal Requirements
59
73
60
-
When confident in your analysis, invoke the submit_proposal tool with four parameters:
74
+
You MUST invoke the submit_proposal tool with four parameters to complete the analysis:
61
75
62
76
- **issue_title**: Short, actionable title for GitHub issue (< 80 characters). Example: "Ruff linting errors in source files"
63
77
- **identified_issue**: Precise description of the root cause (not just the symptom)
0 commit comments