Skip to content

Indicate which test suites are running in a PR comment#4237

Draft
Gedochao wants to merge 3 commits intoVirtusLab:mainfrom
Gedochao:maintenance/comment-which-tests-run
Draft

Indicate which test suites are running in a PR comment#4237
Gedochao wants to merge 3 commits intoVirtusLab:mainfrom
Gedochao:maintenance/comment-which-tests-run

Conversation

@Gedochao
Copy link
Copy Markdown
Contributor

  • a CI job will now post in a comment under PRs which test suites were run
  • separate .github/workflows/pr-classify-comment.yml workflow necessary for this to work on fork PRs (also, this won't run on the current PR until merged, as that workflow needs to be on main - similar to test reports)
  • the included scripts are in Scala; existing scripts for changes CI job were rewritten into Scala CLI scripts as well, with commons extracted.

Checklist

  • tested the solution locally and it works
  • ran the code formatter (scala-cli fmt .)
  • ran scalafix (./mill -i __.fix)
  • ran reference docs auto-generation (./mill -i 'generate-reference-doc[]'.run)

How much have your relied on LLM-based tools in this contribution?

extensively, mostly vibe coded with Cursor

How was the solution tested?

ran some smoke tests locally with the scripts, but generally speaking can't test this end to end without the logic being on main, I'm afraid.

@Gedochao Gedochao force-pushed the maintenance/comment-which-tests-run branch from 64d2eec to 0622d4a Compare April 17, 2026 12:33
@Gedochao Gedochao force-pushed the maintenance/comment-which-tests-run branch 3 times, most recently from 064d4a2 to d151e27 Compare April 17, 2026 13:49
@Gedochao Gedochao force-pushed the maintenance/comment-which-tests-run branch from d151e27 to b06eae4 Compare April 17, 2026 13:51
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.

1 participant