Currently, we use an env variable to point to a gh material URL which is then cloned into /.material .
If someone wanted to use multiple repos we could start cloning 1 level deeper, e.g. /.material/A /.material/B...
These repos could be controlled via a config file in /config e.g.
courses:
A: 'urlA'
B: 'urlB'
possibly add blacklist for sections within those so you can choose to have repo A without course F.
This would require a rework of how gutenberg is deployed, currently we checkout the repo via a github action using a github secret env var. We would need some way to parse the file to checkout instead.
Currently, we use an env variable to point to a gh material URL which is then cloned into /.material .
If someone wanted to use multiple repos we could start cloning 1 level deeper, e.g. /.material/A /.material/B...
These repos could be controlled via a config file in /config e.g.
possibly add blacklist for sections within those so you can choose to have repo A without course F.
This would require a rework of how gutenberg is deployed, currently we checkout the repo via a github action using a github secret env var. We would need some way to parse the file to checkout instead.