chore(ci): add url of the failed wf to the issue body

[tasches]

Summary by CodeRabbit

• Chores
  • Updated workflow notifications to include a direct link to the GitHub Actions run page in issue reports.

[coderabbitai]

"""

Walkthrough

The GitHub Actions workflow for scanning CVEs was updated to append a URL linking to the specific workflow run page in the issue body created by the createIssue job. This URL is constructed from the server URL, repository name, and run ID for direct access to the failed scan details.

Changes

File(s)	Change Summary
.github/workflows/scan-for-cves.yaml	Updated createIssue job to append a workflow run URL to the issue body for failed scans.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant createIssue Job
    participant User

    GitHub Actions->>createIssue Job: Trigger on CVE scan failure
    createIssue Job->>createIssue Job: Construct workflow run URL
    createIssue Job->>createIssue Job: Append URL to issue body
    createIssue Job->>User: Create issue with workflow run link

Loading

Possibly related PRs

• ci(CVE-Reports): create issue if report creation fails #1548: Introduced the createIssue job that this PR modifies by adding the workflow run URL to the issue body.
• ci(scan-for-cves): refactor create issue workflow #1557: Refactored issue creation logic in the same createIssue job within the scan-for-cves workflow.

Suggested reviewers

• cwrau
• marvinWolff

Poem

🐇
A hop and a skip through YAML's green field,
A new link appears, transparency revealed.
Now when CVEs cause a workflow to fall,
A clickable path awaits one and all.
With each little tweak, our burrow grows bright—
Scan, link, and leap into the light!

"""

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 347fac2 and a935520.

📒 Files selected for processing (1)

• .github/workflows/scan-for-cves.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/scan-for-cves.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 856d649 and bba6030.

📒 Files selected for processing (1)

• .github/workflows/scan-for-cves.yaml (1 hunks)

🧰 Additional context used

🪛 GitHub Check: lint github workflows

.github/workflows/scan-for-cves.yaml

[failure] 65-65:
undefined variable "GITHUB_WORKFLOW_URL". available variables are "env", "github", "inputs", "job", "matrix", "needs", "runner", "secrets", "steps", "strategy", "vars"

🪛 GitHub Actions: lint github workflows

.github/workflows/scan-for-cves.yaml

[error] 65-65: actionlint: undefined variable "GITHUB_WORKFLOW_URL". Available variables are "env", "github", "inputs", "job", "matrix", "needs", "runner", "secrets", "steps", "strategy", "vars".

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: wait-for-checks

[cwrau]

If I'm not mistaken the original line would result in Last run of CVE scanning failed. Please check $GITHUB_WORKFLOW_URL for more information instead of expanding it.