Allow contributions from forks?

[maximlt]

This repository has a lot of infrastructure to manage the evaluated examples, the deployments, and the websites. These resources need various secrets that are not made available by Github to PRs opened from a fork, for good security reasons. Enabling this would require quite a lot of work, so for now, the optimal workflow is to add contributors as members of the repo with a write role.

Allow contributions from forks:

• Validate the deployments can be made: need AE5 credentials
  • Maybe this step can be skipped?
• Push the evaluated notebook to a temporary branch: need write permission
  • Stop using Git as a staging area for evaluated notebooks, e.g. push them on S3.
• Deploy the dev site: need Personal Access Token
  • Maybe just skip it?
  • ReadTheDocs can publish a temp dev site per PR (https://docs.readthedocs.io/en/stable/pull-requests.html)

[philippjfr]

Naive question, shouldn't most of the work only be kicked off when the contribution is merged? At which point it will executed within the scope of this repo and have the secrets available?

[maximlt]

It means renouncing building the dev site, doesn't it? I think I didn't go down that route as the former infra had this feature.

[maximlt]

Maybe that could be useful https://github.com/imjohnbo/ok-to-test