-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
What
Ok, so you've finished writing, your version is saved on your computer and you're ready to push up those changes to your branch.
Let's do it.
How
First, make sure all of your changes are saved. Then, run the following in your terminal:
$ git status
$ git add <name of file you changed>
$ git commit "commit message #<githubissuenumber>"
$ git push
Pro-Tips
- Whenever you're working on anything remote, make sure you're up to date on your current branch (if you're working on a team, someone else might be making changes) by running
git pull
. Typically, run this BEFORE you start working on something. - Commit messages are an art. Be specific. Be brief.
- Adding
#10
to your commit message associates your commit to the GitHub issue the commit is supposed to address (GitHub issue Jake 5: Create that New Doc #10 in this repo aka this issue) - Example: Create Sample Doc #13
Metadata
Metadata
Assignees
Labels
No labels