feat(issuegenerator): link to specific failing job instead of workflow run

[vyagh]

Description

Updates the issuegenerator to link directly to the failing job instead of the top-level workflow run summary. This saves maintainers time by taking them straight to the logs of the specific failure.

If a failing job cannot be found (e.g logs expired or API error) or if the run failed immediately, it safely falls back to the existing behavior (linking to the run summary).

Changes

• Added getFailedJobURL to client.go to query the actions/runs/{id}/jobs API.
• Updated templateHelper to use the deep link for ${linkToBuild}.
• Added unit tests covering success, timeout, and fallback scenarios.

Issue

Fixes #1183

Testing

• Unit tests pass (go test ./issuegenerator/...)
• Verified API handles pagination correctly (implied by test logic)

[codecov]

Codecov Report

❌ Patch coverage is 93.02326% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 64.45%. Comparing base (4c93dd4) to head (3c0494c).
⚠️ Report is 13 commits behind head on main.

Files with missing lines	Patch %	Lines
issuegenerator/internal/github/client.go	93.02%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1552      +/-   ##
==========================================
+ Coverage   64.13%   64.45%   +0.31%     
==========================================
  Files          66       66              
  Lines        3424     3463      +39     
==========================================
+ Hits         2196     2232      +36     
- Misses        990      992       +2     
- Partials      238      239       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mx-psi]

We need to update the templates to reflect that we now have a list of failed issues instead of a single link

[mx-psi]

Let's not add timed out as a reason, we know those are not the ones that caused a particular test case to fail

[mx-psi]

Let's add helper text on the template itself

[mx-psi]

As in, here:

opentelemetry-go-build-tools/issuegenerator/internal/github/client.go

Line 62 in 3ef8fab

${failedTests}

[vyagh]

Hi @mx-psi
I pushed an update to address your feedback.
If I misunderstood how you wanted that helper text to look in the template, let me know.

[mx-psi]

Apologies for the delay on this. The main reason I don't feel comfortable merging this PR is because I don't think the failing jobs are on the right place on the issue template. I also worry that there could be too many failing tests and that the message feels 'spammy'.

I would rather keep the original link and have the failing jobs at the bottom of the issue body/comment in a collapsible section.

Since we are changing the issue template, we can also rename linkToBuild (or, rather, add a new field), that really reflects the information we are adding on the issue template (which as a list of links to failing jobs)

[vyagh]

nw about the delay, here's what i did now:

• linkToBuild kept as the workflow run url
• a new failedJobs field that renders a collapsible < details > section at the bottom of the issue/comment
• timed_out jobs are excluded, only failure conclusion is picked up

[mx-psi]

Almost there!

[mx-psi]

Since the details HTML code is fixed I would put it on the template:

Suggested change

	${failedTests}${failedJobs}
	${failedTests}
	<details>
	<summary>Failing job(s)</summary>
	${failedJobs}
	</details>

(same in the other template)

[vyagh]

updated, failedJobs now just returns the list items.

[vyagh]

btw the < details > is in the template now, it'll render an empty collapsible even when there are no failed jobs. are you fine with that?