Some projects can't be built on the CI. This can happen when they need to download too much data or that it just takes too long. They may also require computation resources that aren't available on the CI (e.g. GPU). In that case it's useful to be able to declare that the project should not be built. This is now possible with the skip_project_build special parameter. On top of that this PR changes the way these kind of projects must be submitted. Instead of pushing them directly to the evaluated branch (doing so makes it difficult to track changes), it is expected that the evaluated notebooks should be pushed directly in the PR. It is expected that there shouldn't be too many of these projects, as such, it shouldn't make the repository too big.
Some projects can't be built on the CI. This can happen when they need to download too much data or that it just takes too long. They may also require computation resources that aren't available on the CI (e.g. GPU). In that case it's useful to be able to declare that the project should not be built. This is now possible with the
skip_project_buildspecial parameter. On top of that this PR changes the way these kind of projects must be submitted. Instead of pushing them directly to the evaluated branch (doing so makes it difficult to track changes), it is expected that the evaluated notebooks should be pushed directly in the PR. It is expected that there shouldn't be too many of these projects, as such, it shouldn't make the repository too big.(Disclaimer: not yet fully tested!)