Error in post-init.sh script fails in forked projects whose name is not HS22

Hi @noe.thalheim ,

I am one of the developers of Renku.

I see that a lot of sessions on https://renkulab.io are forking your project. I am assuming that you are teaching a course?

Anyhow, it appears that the post-init.sh script that you wrote in https://renkulab.io/projects/grundkurs-programmieren/hs22 expects the students projects to have the same name as your original project HS22. But when you fork a project the user has the option to rename the project. Some of your students have done this and in this case the post-init.sh script fails and the session cannot start.

Maybe you are aware of this limitation already. In which case you have a few students who did not listen to you. I emailed them to let them know that the post-init script will work only if the project name remains unchanged when forking. I advised them that they can either re-fork again or rename their existing projects.

Hopefully this helps. This is the problematic line: https://renkulab.io/gitlab/grundkurs-programmieren/hs22/-/blob/master/post-init.sh#L37 . If your students have their project named anything other than HS22 then this will setup the upstream as that. For example with a project forked as HS-22-test the script will set the upstream as https://renkulab.io/gitlab/grundkurs-programmieren/HS-22-test.git` but this repository does not really exist and the steps afterwards when you fetch/pull from the upstream will fail.

Hopefully this helps.

I sent this to you as an email as well. Just making sure you see it.