Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitc701816

Browse files
authored
Update git push instructions
Most of the students' first pushes were failing because there wasn't a master branch on their remote.
1 parent512b5bf commitc701816

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ This usually looks like this:
3434
2.`git diff` this will show the actual code that has been changed. Again, we want to make sure we don't push anything to GitHub that shouldn't be there.
3535
3. If everything looks good,`git add nameOfMyFile.js` This adds our file(s) to the 'staging area'
3636
4.`git commit -m "The sentence I want associated with this commit message"` which tells your computer 'hey, next time code is pushed to GitHub, take all of this code with it.'
37-
5.`git push origin master` My code is now on GitHub.
37+
5.`git push-uorigin master` My code is now on GitHub. The`-u` tells GitHub to create a master branch if one doesn't already exist. You can leave it out if the branch you're pushing to already exists.
3838

3939
* If you did this correctly, check your GitHub repository for your new code.
4040

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp