Running Chromatic tests for forked PRs

[leblowl]

I think it would be nice to allow a maintainer to run Chromatic visual regression tests for PRs from forked repos. Currently, it appears that it's necessary to create a branch on the quiet repo.

[holmesworcester]

Sounds good to me. Putting this in "Next sprint" but you can do it whenever!

[Kacper-RF]

I think there are two solutions:

1. External collaborator should add chromatic secret to his settings in forked repository.
2. Marek suggested that if You(Holmes) give this token to external collaborators when they ask, maybe it should be plain text ? It will probably completely remove the problem of running this workflow by other collaborators, but I know this may not be optimal for security reasons.

[holmesworcester]

I don't understand what you mean by plain text. You mean just put it in the repo?

[Kacper-RF]

Yes

[holmesworcester]

I have to check if chromatic has capped billing, or if there are other potential security issues.

I really don't like it, by default.

Can we run these tests ourselves for outside contributors?

[siepra]

@holmesworcester Chromatic's documentation says for oss forks we should just commit the project token as plaintext
https://www.chromatic.com/docs/github-actions#run-chromatic-on-external-forks-of-open-source-projects

[holmesworcester]

Okay let's do it!

[Kacper-RF]

#1862
forked: #1820