You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the addition of the 2nd branch of code to the demonstration repository, we need participates to fork the repository, rather than use the template. This raises the issue that all student repositories will be linked to ours, and PR's will, by default, go to our repository.
Should we look at methods for detaching the forked repositories, to avoid this problem?
I have tested this out with GitHub support, and they will do this for us, however it takes several hours, and they suggested the alternative below.
With the addition of the 2nd branch of code to the demonstration repository, we need participates to fork the repository, rather than use the template. This raises the issue that all student repositories will be linked to ours, and PR's will, by default, go to our repository.
Should we look at methods for detaching the forked repositories, to avoid this problem?
I have tested this out with GitHub support, and they will do this for us, however it takes several hours, and they suggested the alternative below.
Alternative is to do this manually, following this process https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork:
git clone --bare https://github.com/EXAMPLE-USER/FORK-NAME.git
git push --mirror https://github.com/EXAMPLE-USER/FORK-NAME.git
Would this be too complicated for our students?
The text was updated successfully, but these errors were encountered: