Link generation
Instructor guide to generate links for easy distribution of materials
Last updated
Instructor guide to generate links for easy distribution of materials
Last updated
nbgitpuller is a tool lets you distribute content in a git repository to your students by having them click a simple link. It relies on automatic, opinioned conflict resolution that ensures that your students are never exposed to git directly. This tools comes pre-installed in your JupyterHub.
If you are not familiar with git and GitHub, we recommend you visit the Git section of this documentation. Before you can start using nbgitpuller you will need a GitHub account and a repository that you wish to distribute to your students.
Once you have a repository with the material that you wish to distribute, you can generate an nbgitpuller links with the generator. The requirements of the generator are depicted and explained below. The circled locations required special attention
This is the link generated. It can be copied and sent to your students
The url of your hub
The git repository where you have published your content. Please notice that the url can start either with git:// or https://. If you are not expencting your students to have configured github authentication/ssh keys nor have a GitHub account, make sure you use https://.
Notice that your URL does not end in .git. (This is often the case if you are pasting URL from GitHub)
The branch of the repository you wish to distribute
Optionally, a particular file or directory you want to automatically open for your students once the repository has been synchronized.
Choose the JupyterLab interaface as this is the default for all of Brown's Hubs
Select the Default version of the link, even if distributing the link via Canvas
The first time a particular student clicks the link, a local copy of the repository is made for the student. On successive clicks, the latest version of the remote repository is fetched, and merged automatically with the student’s local copy using a series of rules that ensure students never get merge conflicts.
You are running a JupyterHub for a class & want an easy way to distribute materials to your students without them having to understand what git is.
You have a different out of band method for collecting completed assignments / notebooks from students, since they can not just ‘push it back’ via git.
You are an instructor using a JupyterHub / running notebooks locally to create materials and push them to a git repository. You should just use git directly, since the assumptions and design of nbgitpuller will surprise you in unexpected ways if you are pushing with git but pulling with nbgitpuller.
Your students are performing manual git operations on the git repository cloned as well as using nbgitpuller. Mixing manual git operations + automatic nbgitpuller operations is going to cause surprises on an ongoing basis, and should be avoided.
