Setup of GitHub repository for in-class sessions

  1. Create a new repository on GitHub. Use the following settings:

    • Repository name: eds220-in-class.

    • Description: In-class work for the EDS 220 MEDS course.

    • Visibility: Keep the repository public.

    • Don’t select any template to start.

    • Add a README file.

    • Add a Python .gitignore template.

    • Add the MIT License.

  2. In GitHub, update your repository’s README by:

    1. Deleting all the text that was automatically generated when you created the repo.
    2. Copy-pasting the markdown text below and update [YOUR NAME HERE]. Commit your changes.
# EDS 220 In-Class Repository

This repository hosts all the work completed by [YOUR NAME HERE] during the EDS 220 - *Working with Environmental Data* lectures.

## Course Information

- **Course Title:** [EDS 220 - Working with Environmental Datasets](https://bren.ucsb.edu/courses/eds-220)
- **Term:** Fall 2026
- **Program:** [UCSB Masters in Environmental Data Science](https://bren.ucsb.edu/masters-programs/master-environmental-data-science).

Teaching Team:

- **Instructor:** [Carmen Galaz García](https://github.com/carmengg)
- **TA:** [Fatiq Nadeem](https://fatiqnadeem.com) 

Complete materials for the discussion sections and additional resources can be found on the [course website](https://meds-eds-220.github.io/MEDS-eds-220-course/).
  1. Add the URL to your GitHub repository to this spreadsheet.

2. Clone the repository

  1. At Bren’s workbench 1 server, start a new JupyterLab session or access an active one.

  2. In the terminal, navigate into your EDS-220 directory.

  3. Using the terminal, clone the eds220-in-class repository into your EDS-220 directory.

3. Configure git pull.rebase

If you already configured git pull.rebase globally on the workbench in Discussion Section 0, you can skip this step. Otherwise, configure the way git handles git pull by running in the terminal

git config --global pull.rebase false

4. Recap

After following the set up for the in-class and discussion section repositories, your file structure shoudl look like this (the notebook is an example):

EDS-220/
├── eds220-discussion-sections/
│   ├── README.md
│   ├── LICENSE
│   └── .gitignore
│
└── eds220-in-class/
    ├── README.md
    ├── LICENSE
    ├── .gitignore
    ├── data/
    └── week0-python-review.ipynb

Scubatocat by cameronfoxly. Octocat is a registered trademark of GitHub, Inc.; the octocat images are not covered by this website’s CC BY-NC 4.0 license.