Skip to content

Update push-trigger.yml#113

Merged
swatigoel merged 1 commit into
inji:developfrom
rajapandi1234:patch-1
Mar 16, 2026
Merged

Update push-trigger.yml#113
swatigoel merged 1 commit into
inji:developfrom
rajapandi1234:patch-1

Conversation

@rajapandi1234

@rajapandi1234 rajapandi1234 commented Mar 16, 2026

Copy link
Copy Markdown

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflow configuration to reference a specific version for more consistent and reliable continuous integration builds.

Signed-off-by: Rajapandi M <138785181+rajapandi1234@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Mar 16, 2026

Copy link
Copy Markdown

Walkthrough

Updated a GitHub Actions workflow file to reference the gradlew-sonar-analysis workflow by specific commit hash instead of a branch name. This change pins the workflow version to a particular commit rather than tracking branch updates.

Changes

Cohort / File(s) Summary
Workflow Configuration
.github/workflows/push-trigger.yml
Updated workflow reference from branch master-java21 to commit hash dsd9685 for the gradlew-sonar-analysis workflow trigger.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A rabbit hops through workflows so grand,
From branches to commits, we understand,
A hash now anchors our sonar test,
Pinning precision—we know what's best!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Update push-trigger.yml' is vague and generic, using non-descriptive language that only mentions the file name without explaining the actual change (updating workflow reference from branch to commit hash). Revise the title to be more specific about the actual change, such as 'Update push-trigger.yml workflow reference to specific commit hash' to clearly communicate the primary modification.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/push-trigger.yml:
- Line 34: The workflow currently pins the reusable workflow using a short ref
"uses: mosip/kattu/.github/workflows/gradlew-sonar-analysis.yml@dsd9685";
replace that suffix with the full 40-character commit SHA of the exact commit
you want to pin (e.g., ...gradlew-sonar-analysis.yml@<40-char-sha>) so the
reusable workflow is immutably pinned; locate the uses: line in the
push-trigger.yml and update it to reference the full commit SHA (you can obtain
the SHA from the upstream repo via git ls-remote or the commit history on
GitHub).

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 38201e72-039d-49a0-a099-a8abba0d77e6

📥 Commits

Reviewing files that changed from the base of the PR and between 6933085 and 08ddf3e.

📒 Files selected for processing (1)
  • .github/workflows/push-trigger.yml

Comment thread .github/workflows/push-trigger.yml
@swatigoel swatigoel merged commit e53f30a into inji:develop Mar 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants