Add download link on PRs for easier testing

[azatsarynnyy]

Once the PR checks are green, the comment appears on the PR with the link to download the built artifact:

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 95ad3127-2a09-497c-a326-bb8f1bef76be

📥 Commits

Reviewing files that changed from the base of the PR and between 9f7b425 and 7a8ab4c.

📒 Files selected for processing (1)

• .github/workflows/build.yml

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Automated pull request comments now include direct download links for workflow run artifacts.

Walkthrough

This pull request adds a new GitHub Actions workflow job that automatically posts comments on pull requests with links to download build artifacts. The job waits for the build, test, code inspection, and verification jobs to complete before posting the comment using the GitHub CLI.

Changes

PR Artifact Comment Automation

Layer / File(s)	Summary
Add prComment job with artifact download link .github/workflows/build.yml	New prComment job runs after build/test/inspectCode/verify complete on pull requests, then posts a PR comment with a dynamically generated download link to the plugin artifact using gh pr comment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess whether a description exists.	Add a pull request description explaining the purpose, implementation details, and any relevant testing information for the prComment job.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding a download link to pull requests to facilitate easier testing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.1.0
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[github-actions]

✅ Build successful! For testing, download plugin zip from the Artifacts section.

[azatsarynnyy]

@adietish @vrubezhny WDYT about such a small improvement of manual testing flow?

[vrubezhny]

@adietish @vrubezhny WDYT about such a small improvement of manual testing flow?

A nice improvement! Thanks!

[vrubezhny]

Looks good to me. A nice improvement, thanks!