chore: Update for workflow name

[sagar-qa007]

Description

Update name of the workflow for each search and visibility.

Tested on my forked repository:

Fixes # Issue Number

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

[coderabbitai]

Walkthrough

The workflow file .github/workflows/test-vulnerabilities-data.yml has been updated to change its name and structure. The workflow is now titled "Run Vulnerability" and includes a new run-name field that dynamically reflects the branch and Docker image name. It can be manually triggered with an input parameter image_name, which is mandatory. The existing job structure remains unchanged, continuing to check out the repository, set up Node.js, and run vulnerability scripts while maintaining the same environment variables and parameters.

Changes

File Path	Change Summary
.github/workflows/test-vulnerabilities-data.yml	- Workflow name changed to "Run Vulnerability". - Added run-name field for dynamic branch and Docker image name. - Introduced mandatory input parameter image_name in workflow_dispatch.

Possibly related PRs

• chore: Added scout & trivy scan to github workflow #37022: Adds Scout and Trivy vulnerability scans to the GitHub workflow.
• chore: New schema change for vulnerabilities test #37204: Modifies the same workflow file by removing a step that fetched vulnerability data from a PostgreSQL database.
• chore: Adding step for install #37276: Adds an installation step related to the vulnerability scanning process.
• chore: Minor change for log in workflow #37346: Enhances logging for new vulnerabilities detected by Scout and Trivy in the workflow file.

Suggested labels

Task, skip-changelog, ok-to-test

Suggested reviewers

• sharat87
• yatinappsmith

In a workflow where vulnerabilities hide,
A new name and structure, we now abide.
With a branch and image, the checks are tight,
Our code stays safe, and all feels right!
So let’s run the tests, with joy and cheer,
For security’s sake, we persevere! 🎉

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

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: 0

🧹 Outside diff range and nitpick comments (1)

.github/workflows/test-vulnerabilities-data.yml (1)

1-1: Remove trailing space

Remove the trailing space at the end of line 1.

-name: Run Vulnerability 
+name: Run Vulnerability

🧰 Tools

🪛 yamllint (1.35.1)

[error] 1-1: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b778d2c and d2962f3.

📒 Files selected for processing (1)

• .github/workflows/test-vulnerabilities-data.yml (1 hunks)

🧰 Additional context used

🪛 yamllint (1.35.1)

.github/workflows/test-vulnerabilities-data.yml

[error] 1-1: trailing spaces

(trailing-spaces)

🔇 Additional comments (3)

.github/workflows/test-vulnerabilities-data.yml (3)

3-4: LGTM! Improved workflow visibility

The new run-name provides better visibility by showing the branch and image name in the GitHub Actions UI.

---

Line range hint 6-13: LGTM! Well-structured input configuration

The input parameter configuration is consistent with its usage in the run-name and provides appropriate defaults.

🧰 Tools

🪛 yamllint (1.35.1)

[error] 1-1: trailing spaces

(trailing-spaces)

---

Line range hint 15-89: Verify script permissions in repository

The workflow relies on executing shell scripts. Let's verify that these scripts maintain their executable permissions in the repository.

✅ Verification successful

Scripts have correct executable permissions

The vulnerability scanning scripts in the repository already have the correct executable permissions (755 - rwxr-xr-x) set, making the chmod +x commands in the workflow redundant but harmless.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if vulnerability scanning scripts have executable permissions

echo "Checking script permissions..."
ls -l scripts/scout_vulnerabilities_data.sh scripts/trivy_vulnerabilities_data.sh 2>/dev/null || \
echo "Warning: Scripts not found or permissions not set correctly"

Length of output: 328

🧰 Tools

🪛 yamllint (1.35.1)

[error] 1-1: trailing spaces

(trailing-spaces)