Ctrl+K

Basic setup

Basic setup#

1. Fork projects repository#

Before you start working on your group projects. You should fork eScience2024-projects repo. To make a fork, go to the repo page. There you will see a fork button fbutton. Click on it to create a copy of this repository in your github user space. Uncheck Copy the main branch only if you do not want to miss on other branches currently on the original repo.

Fork Creation page

2. Get GitGub Access token#

From GitHub documentation.

  • Go to Github.

  • Click on your your profile image in the top-right.

  • Click Settings

  • Click Developer Settings

  • Click Personel access tokens->Tokens (classic)

  • Click Generate new token

  • Click Generate new token (classic)

  • Authenticate

  • Make a note

  • Click on repo, user

  • Click generate

  • Save token somewhere, treat it as a password

3. Setup git and clone on jupyterhub#

After you have forked the projects repo you should login to Jupyterhub. There, you would need to clone your fork and create your first branch you would be working on. See Starting with git on the jupyterhub.

Attention

If you have already accessed test sever, you should move to https://escience2024.craas1.sigma2.no. Test server is only there for testing and will get shutdown.

  • Open terminal through Launcher.

  • Type this commands filling in your github username and email (without <>):

    git config --global user.name "<your_username>"
git config --global user.email "<your_email>"

  • Clone your fork of projects repository:

    git clone https://github.com/<your_username>/eScience2024-projects

  • Go into your clone:

    cd eScience2024-projects

  • Add upstream repository (See Setting up remotes):

    git remote add upstream https://github.com/MetOs-UiO/eScience2024-projects
git fetch --all

  • Make your first branch with a sensible name (what are you going to work on). Below you first checkout the current state of the upstream (the main repo, not your fork), and then add a branch (which will then be up to date with the main branch on the main repo) and switch to it, and finally you push your new local branch to the remote origin (which is your fork).

    git checkout upstream/main
git switch -c <sensible-branch-name>
git push origin <sensible-branch-name>

4. Sharing your work within the group#

Within your fork, you should put all your code in your Group# folder.

When you need to share your work with the others within your group you need to make a Pull Request to the upstream repo main branch.

After a Teaching assistant responsible for you group has merged your PR to upstream/main other members of your group can pull these changes into branches on their forks to work on.

In addition, you will most likely want to create new branches based on the updated upstream/main. See Setting up remotes.

Contents