Skip to content

Conversation

@Prafulrakhade
Copy link
Contributor

@Prafulrakhade Prafulrakhade commented Jan 14, 2026

Summary by CodeRabbit

  • Chores
    • Fixed GitHub Actions workflow configuration to ensure proper CI/CD pipeline execution.

✏️ Tip: You can customize this high-level summary in your review settings.

Signed-off-by: Praful Rakhade <prafulrakhade02@gmail.com>
@coderabbitai
Copy link

coderabbitai bot commented Jan 14, 2026

Walkthrough

A GitHub Actions workflow file is updated to correct a branch reference in the publish-snapshot job, changing from "Mmaster" to "master" for the reused-workflow invocation. This aligns the workflow reference with the standard branch naming convention.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow Configuration
.github/workflows/kotlin-artifacts-build.yml
Updated branch reference from "Mmaster" to "master" in the publish-snapshot job's uses directive for the reused-workflow call

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • ckm007

Poem

🐰 Master of workflows, no more the typo's sting!
From "Mmaster" to "master," clarity we bring,
One line to fix, the reference now true,
Artifacts shall publish—hopping brand new!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title references 'maven-publish-android-download.yaml' but the actual file changed is '.github/workflows/kotlin-artifacts-build.yml' - these are different files, making the title misleading. Update the PR title to accurately reflect the actual file being modified: '.github/workflows/kotlin-artifacts-build.yml' or provide context about why this file name appears in the title.
✅ 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.


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.

@Prafulrakhade Prafulrakhade merged commit 550ea61 into inji:develop Jan 14, 2026
4 of 5 checks passed
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @.github/workflows/kotlin-artifacts-build.yml:
- Around line 34-37: The reusable workflow reference in the publish-snapshot job
points to a non-existent file `maven-publish-android.yml` in the `mosip/kattu`
repo; update the `uses:
mosip/kattu/.github/workflows/maven-publish-android.yml@master` to reference the
correct existing workflow (likely `maven-publish-to-nexus.yml`) or the correct
repository/file that actually contains the intended publish workflow, ensuring
the `uses:` entry matches an existing filename in the target repo.
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aba3615 and 5563dba.

📒 Files selected for processing (1)
  • .github/workflows/kotlin-artifacts-build.yml

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.

Comment on lines 34 to 37
publish-snapshot:
if: ${{ inputs.release_type == 'snapshot' }}
uses: mosip/kattu/.github/workflows/maven-publish-android.yml@Mmaster
uses: mosip/kattu/.github/workflows/maven-publish-android.yml@master
with:
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

mosip/kattu github repository workflows maven-publish-android

💡 Result:

Do you want me to: (A) locate and show the maven-publish-android workflow file from mosip/kattu on GitHub, (B) explain how that workflow works, or (C) help you create/fix a similar GitHub Actions workflow?


🌐 Web query:

mosip/kattu GitHub repository master branch

💡 Result:

The mosip/kattu repository (workflows for building MOSIP projects) is on GitHub: https://github.com/mosip/kattu. See MOSIP docs referencing kattu and an index listing the repo. [1][2]

Sources:

  • MOSIP docs (references to kattu in GitHub workflow / Java21 migration). [1]
  • Repository listing (mosip owner repos includes "mosip/kattu"). [2]

🌐 Web query:

mosip/kattu .github/workflows/maven-publish-android.yml

💡 Result:

Do you want the file's contents, a link to the GitHub file, or information about what that workflow does?


🌐 Web query:

site:github.com/mosip/kattu maven-publish-android.yml workflows

💡 Result:

I couldn't find a file named maven-publish-android.yml in the mosip/kattu workflows. The repository's workflow list includes files such as maven-publish-to-nexus.yml and npm-android-build.yml, but not maven-publish-android.yml. [1][2]

Sources:

  • mosip/kattu repository (workflows list). [1]
  • maven-publish-to-nexus workflow README in mosip/kattu. [2]

🌐 Web query:

mosip/kattu github workflows directory list maven-publish

💡 Result:

Do you want me to list the files in .github/workflows of the mosip/kattu repository (and highlight those that use maven-publish), or search the whole repo for "maven-publish"?


🌐 Web query:

site:github.com/mosip/kattu/.github/workflows

💡 Result:

I found the mosip/kattu GitHub repo and its .github/workflows files. The workflow filenames are:

  • chart-lint-publish.yml
  • clear-artifacts.yml
  • codeql-analysis.yml
  • docker-build.yml
  • gradlew-sonar-analysis.yml
  • image-transfer.yml
  • maven-build.yml
  • maven-publish-to-nexus.yml
  • maven-sonar-analysis.yml
  • npm-android-build.yml
  • npm-build.yml
  • npm-publish-to-npm-registry.yml
  • npm-sonar-analysis.yml
  • post-release-changes.yml
  • release-changes.yml
  • tag.yml

Source: mosip/kattu repository (workflows list). [1][2]

References:
[1] GitHub — mosip/kattu (workflows list).
[2] Repository index summary for mosip/kattu.


🌐 Web query:

mosip/kattu maven-publish-android-download workflow

💡 Result:

Do you want the actual mosip/kattu GitHub Actions workflow file named maven-publish-android-download, or help to create/configure a workflow that publishes Android artifacts via maven-publish and downloads them?


The referenced reusable workflow file does not exist; this will fail at runtime.

The typo fix from @Mmaster to @master is correct, but the workflow file maven-publish-android.yml does not exist in the mosip/kattu repository. The complete .github/workflows directory in mosip/kattu contains only these files: chart-lint-publish.yml, clear-artifacts.yml, codeql-analysis.yml, docker-build.yml, gradlew-sonar-analysis.yml, image-transfer.yml, maven-build.yml, maven-publish-to-nexus.yml, maven-sonar-analysis.yml, npm-android-build.yml, npm-build.yml, npm-publish-to-npm-registry.yml, npm-sonar-analysis.yml, post-release-changes.yml, release-changes.yml, and tag.yml.

Verify that the intended workflow exists in mosip/kattu or update the reference to point to the correct file (likely maven-publish-to-nexus.yml).

🤖 Prompt for AI Agents
In @.github/workflows/kotlin-artifacts-build.yml around lines 34 - 37, The
reusable workflow reference in the publish-snapshot job points to a non-existent
file `maven-publish-android.yml` in the `mosip/kattu` repo; update the `uses:
mosip/kattu/.github/workflows/maven-publish-android.yml@master` to reference the
correct existing workflow (likely `maven-publish-to-nexus.yml`) or the correct
repository/file that actually contains the intended publish workflow, ensuring
the `uses:` entry matches an existing filename in the target repo.

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