-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add pkg.pr.new
#6362
chore: add pkg.pr.new
#6362
Conversation
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
.github/workflows/cr-comment.yml
Outdated
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- run: gh issue edit ${{ github.event.issue.number }} --add-label cr-tracked --repo ${{ github.repository }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, what is this for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will add the cr-tracked
label once received /publish
PR comment, check vite-pwa/vite-plugin-pwa#742
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ohhh, makes sense! Thank you so much!
I love this. |
@userquin We discussed about how to trigger pkg.pr.new and we agreed "cr-tracked" label based workflow is okay. I'll push a few commits here and see how it goes. |
@sheremet-va We haven't installed the app yet? https://github.com/vitest-dev/vitest/actions/runs/11050071341/job/30697038656?pr=6362#step:7:13
|
We didn't install anything |
Should be installed now |
you need to add the app to vitest repo: https://github.com/stackblitz-labs/pkg.pr.new?tab=readme-ov-file#setup |
@vitest/coverage-istanbul
@vitest/browser
@vitest/coverage-v8
@vitest/expect
@vitest/pretty-format
@vitest/mocker
@vitest/spy
@vitest/snapshot
@vitest/runner
@vitest/utils
@vitest/ui
vite-node
@vitest/web-worker
@vitest/ws-client
vitest
commit: |
Check vitepress repo, using vue bot, check |
@userquin |
@hi-ogawa I've sent you an invitation to vue discord server and a link to Vitepress room/channel, I asked
|
We don't want to add labels automatically. The idea is that the maintainer adds a label to allow CR manually |
Yeah, I just also checked re-labeling "cr-tracked" and this alone can also trigger CR correctly. https://github.com/vitest-dev/vitest/actions/workflows/cr.yml |
I tested a few examples locally and also on stackblitz and it looks working https://stackblitz.com/edit/vitest-dev-vitest-ei9jaw?file=package.json |
… into userquin/chore-add-pkg-pr-new
For reference, adding the label automatically refers to this scheme: I think adding a label instead of a comment is quite nice too, so good to move forward with this PR as is. I think in Vite we'll keep the comment (with the label workaround). We can try both approaches and see what ends up working best. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a mention in the readme/documentation that we have this? We have this for example: https://vitest.dev/guide/#using-unreleased-commits
https://github.com/vite-pwa/vite-plugin-pwa/blob/main/.github/pull_request_template.md |
The comment can only be added by the maintainers We also publish every commit on |
… into userquin/chore-add-pkg-pr-new
I just pushed a few commits but EDIT: Oh, it got OOM https://github.com/vitest-dev/vitest/actions/runs/11115894967/job/30885165567#step:7:22 |
interesting, can you trigger a re-run for the failed workflow? |
Thanks for the help. I started a re-run and it looks like it's still stuck. |
That's bad, I'll just have a look soon! |
I think it is fixed now, feel free to trigger a re-run! |
@Aslemammad Thanks! I confirmed pkg-pr-new is working now https://github.com/vitest-dev/vitest/actions/runs/11115894967/job/30904769639?pr=6362 |
Happy to hear that ❤️ |
Description
This PR includes:
update PR template to include/publish
tipadd CR comment workflow via/publish
(tip on the PR template)cr-tracked
label PR or main branch pushThis PR requires:
cr-tracked
labeladdCR_PAT
secret to Actions with a token withpublic_repo
(Classic Token): later we can automate it with something like this https://github.com/vitest-dev/vitest/blob/main/.github/workflows/ecosystem-ci-trigger.yml#L63C1-L68 (I'm a newbye on GH actions/webflows)This PR requires also a review to exclude CR for
docs
for example, we can use something like this inon.pull_request
:/cc @Aslemammad
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yaml
unless you introduce a new test example.Tests
pnpm test:ci
.Documentation
pnpm run docs
command.Changesets
feat:
,fix:
,perf:
,docs:
, orchore:
.