Skip to content

Repository Clean Forking #50

@douglowe

Description

@douglowe

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:

  1. fork
  2. clone locally git clone --bare https://github.com/EXAMPLE-USER/FORK-NAME.git
  3. delete fork
  4. push back to same location as before, to create a new repository git push --mirror https://github.com/EXAMPLE-USER/FORK-NAME.git

Would this be too complicated for our students?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions