Skip to content

ci: upload Vitest results to their own Currents project - #4

Merged
agoldis merged 1 commit into
mainfrom
currents/vitest-project
Nov 12, 2026
Merged

agoldis merged 1 commit into
mainfrom
currents/vitest-project

Conversation

@agoldis

@agoldis agoldis commented Nov 12, 2026 •

Copy link
Copy Markdown

Owner: @agoldis

What

The trusted upload workflow sends Vitest unit and Postgres results to the Currents project Rakazo-vitest instead of Rakazo, which keeps the Playwright runs.

Changes

  • currents-upload.yml reads vars.CURRENTS_VITEST_PROJECT_ID (set to the new project). The record key is the same.

Tested

Not run yet: the upload workflow runs from main, so the first upload to the new project is the CI run after this merges.

🤖 Generated with Claude Code

https://claude.ai/code/session_011baD3iKo43DsfhRB8dkWCG


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Playwright and Vitest runs land in separate Currents projects:
Rakazo (CURRENTS_PROJECT_ID) and Rakazo-vitest
(CURRENTS_VITEST_PROJECT_ID).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011baD3iKo43DsfhRB8dkWCG
@agoldis
agoldis merged commit a142cb8 into main Nov 12, 2026
32 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.

1 participant