Skip to content

prompts: linkify code refs in investigate.md #164154

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
trunk-io merged 1 commit into from
Feb 23, 2026
Merged

prompts: linkify code refs in investigate.md #164154

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
5 changes: 5 additions & 0 deletions .github/prompts/investigate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,11 @@ top-level error is just "command failed" or similarly uninformative,
dig into the artifact logs to find the actual underlying failure
from the command's output.>

<When referencing file:line(s) in code, make it a link specific to this repo and
Copy link
Member

@tbg tbg Feb 23, 2026

Choose a reason for hiding this comment

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

This seems to be the wrong place (you're in the kind of "template section" of the prompt). I'd expect advice like this at around line 207.

Copy link
Collaborator Author

@pav-kv pav-kv Feb 23, 2026

Choose a reason for hiding this comment

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

I was hoping to avoid too many links (like in all the code walkthrough in Analysis), so put it in this section where it is most needed (to jump straight to the test code / failure).

Not feeling strongly, can move. I can probably ask it to be not too aggressive with linking everything.

Copy link
Member

@tbg tbg Feb 23, 2026

Choose a reason for hiding this comment

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

This works for me!

SHA. Example:
[server.go:251](https://github.com/cockroachdb/cockroach/blob/<sha>/pkg/server/server.go#L251).
For multi-line sections, e.g. [server.go:251-300], use suffix like #L251-L300>

### Analysis

<Your hypotheses about the failure, ordered by likelihood. For each:
Expand Down