That PR got a bit wild, moving around and touching the Github workflows isn't something that can easily be tested locally. Main changes include:
Before to build a project a special message had to be committed (commit:{projectname}). When detected, the build would be triggered and would, if successful, push the evaluated content to the evaluated branch. This had two main problems: 1) it was easy to forget and 2) it opened the door to race conditions (PR A and PR B modifying evaluated at the same time, PR A being merged with the changes from B that isn't yet merged). As such this PR removes this mechanism and instead:
automatically detects what projects changed, it then tests them (validation + project tests) and builds them if the tests were successful
the build artifacts are no longer pushed to evaluated but to a temporary branch named tmp_evaluated_{sourcebranchname}
the dev website is built if the builds succeed. It pulls the built artifacts from both the temporary branch and evaluated
the evaluated content is pushed to evaluatedonly when the PR is merged, right after that the main site is built
Moves the steps that creates the projects archives and move the thumbnails from the build workflow to the docs workflow, as these artifacts don't need to be pushed to the evaluated branch.
Makes the data source more explicit by asking projects that don't need to ingest any data (either via the downloads: section, using an Intake catalog or having a data/ folder) to declare it
Add more "linters" (e.g. thumbnails aspect ratio and bytes size)
This needs more testing and will certainly require some follow-up PRs.
That PR got a bit wild, moving around and touching the Github workflows isn't something that can easily be tested locally. Main changes include:
commit:{projectname}). When detected, the build would be triggered and would, if successful, push the evaluated content to the evaluated branch. This had two main problems: 1) it was easy to forget and 2) it opened the door to race conditions (PR A and PR B modifying evaluated at the same time, PR A being merged with the changes from B that isn't yet merged). As such this PR removes this mechanism and instead:tmp_evaluated_{sourcebranchname}downloads:section, using an Intake catalog or having adata/folder) to declare itThis needs more testing and will certainly require some follow-up PRs.