Skip to content
This repository was archived by the owner on May 16, 2022. It is now read-only.
This repository was archived by the owner on May 16, 2022. It is now read-only.

Participants don't realise they only need to set up the git remote once. #21

@36degrees

Description

@36degrees

This issue was observed whilst facilitating Prototype Kit training in Manchester on 20 February 2020.

At least one participant did not realise that they only needed to set up the GitHub remote once, and that when they wanted to push changes in the future they could jump straight to git push -u origin master.

Because they had already had a remote with that name, they were getting an error message that they did not understand when they were trying to set up the remote again.

1. Go to the remote repo in GitHub. This is the empty repo created earlier.
1. Select the __Clone or download__ button.
1. Select __Use HTTPS__ .
1. Select the copy button.
1. Back in the command line, link the local repo to the remote repo by typing:
```
git remote add origin REMOTE-REPO-URL
```
Where `REMOTE-REPO-URL` is the copied URL.

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