'Agile' Data School activity

3. A work sprint

(2.5 hours)

Time for action! We’re going to address some of these tasks ourselves, this afternoon.

Everyone should take a task to work on, preferably one originally written by someone else in the group.

Most of the Data School teaching material exists as text files in GitHub repositories (links) and thus can be easily edited by anyone, by making a fork to have your own copy. Forking on GitHub is very similar to what you saw previously with Bitbucket.

Instructors can help with creating a fork of a lesson on GitHub, creating a local clone and understanding the files involved.

Make sure you’ve checked out the correct branch*, create a new branch for your own work and then…

Make changes to file(s) to complete your task.
Push the change back to your forked remote repository (origin).
On GitHub, create a Pull Request that would merge your changes back to the base branch
-Use this Pull Request to describe the change you made and why
-Save the Pull Request, but don’t Merge it (we’ll review together later)
If more time, start another task?

* Lessons using the older Carpentries template use a branch named ‘gh-pages’, while lessons using the newer Carpentries template (and most other repositories) use a ‘main’ branch.

« Back