-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #19 from MWiehr/main
Added new picture and text from the issue
- Loading branch information
Showing
3 changed files
with
4 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,11 +18,15 @@ Putting your code on GitHub confers a number of benefits: | |
<img src="assets/new_repo.png" width="600"> | ||
|
||
At the **Create a new repository** screen, give your repo a name and click **Create Repository**. | ||
In this case only, when you didn't start by creating a repo on GitHub but want to push from an exisiting local reposiotry for the first time like we are doing now and like you would to upgrade your old projects, do NOT select 'create a README file' but directly 'Create repository | ||
|
||
![](./assets/new_repo_name.png) | ||
|
||
The **Quick Setup** screen gives sets of git commands that can be used in various circumstances. | ||
First, make sure you select the SSH tab (the url shown in the blue box should start with [email protected]). | ||
|
||
|
||
|
||
We are then interested in **…or push an existing repository from the command line**. Copy these commands to the clipboard using the copy button on GitHub. | ||
|
||
![](./assets/github_git_commands.png) | ||
|