Closed padasch closed 1 year ago
There is only one website allowed on github pages - per repository. So put simply, we can't do this in this setup. Alternatively, you can setup an action which monitors release on the agds repo, which then triggers a render in another repo. This is how the automation of sofunCalVal
works. Now, this complicates maters a bit as the URL has already been shared. So, for now leave as is IMO.
Now, I do agree that we should make a tag/release and save this one for reference (and or a DOI on zenodo).
During this semester I would aggregate all issues and leave be until after the course is over, these few months won't make a difference (especially in light of all the merge conflicts that might arise). We should let this rest for a bit as well, to get some perspective.
I made a FAQ to host some of these questions and remarks (maybe FAQ isn't the right name then). See #85
@stineb @pepaaran
I guess there will be issues raised and problems resolved throughout the semester. Instead of piling them up, continual improvement would be good. Can we fix the rendered book to a tag?
But if the published book is fixed to a tag and we want to update changes and see if the book still runs, we would need a separate compilation for the new commit. Is it possible to have a stable public version and a development version under a different URL?
Of course we can resolve errors on our forks but that could result in various merge conflicts later on...