Someone is attempting to deploy a commit to the napari Team on Vercel.

A member of the Team first needs to authorize it.

@tlambert03 I'm not sure what's needed here on the vercel side, but would you be able to add/transfer credentials for it in the 1password vault?

Can you also confirm where the changes in this PR will be written i.e. will the workflows actually write to the published public/ folder or do they not write anywhere? I couldn't find an option to toggle the destination based on where the workflow is running.

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Can you also confirm where the changes in this PR will be written i.e. will the workflows actually write to the published public/ folder or do they not write anywhere?

this line writes extended_summary.json to the public folder in this repo. This line commits the changes to the repo

but would you be able to add/transfer credentials for it in the 1password vault?

i'm not sure vercel works like that, but @Czaki is listed as an owner of the team

... and it won't let me add more members to the team without upgrading my plan. Since @Czaki already has access, perhaps he can figure out how to share/transfer/whatever. I'm happy to leave the team if it helps. just let me nkow

(in any case, it will always publish on main i think... so you don't need to worry about it. it's only if you want to preview the published page from a PR)

Based on this, what I remember and what is suggested by documentation https://vercel.com/docs/accounts/create-a-team it is enough to create vercel account using GitHub authorization and people from core-dev should be added to organization on vercel.

Hmmm if I run stuff locally, visibility is there and I can see that the empty pypi version packages are excluded, but if I look at the published preview from vercel the extended summary doesn't have the info... @Czaki ideas?