|
This command updates the index using the current content found
in the working tree, to prepare the content staged for the next
commit. It typically adds the current content of existing paths
as a whole, but with some options it can also be used to add
content with only part of the changes made to the working tree
files applied, or remove paths that do not exist in the working
tree anymore.
|
Git commit creates a commit, which is like a snapshot of your
repository. These commits are snapshots of your entire
repository at specific times. You should make new commits often,
based around logical units of change. Over time, commits should
tell a story of the history of your repository and how it came
to be the way that it currently is. Commits include lots of
metadata in addition to the contents and message, like the
author, timestamp, and more.
|
The git push command is used to upload local repository content
to a remote repository. Pushing is how you transfer commits from
your local repository to a remote repo. It's the counterpart to
git fetch, but whereas fetching imports commits to local branches,
pushing exports commits to remote branches. Remote branches are
configured using the
git remote
command. Pushing has the potential to overwrite changes, caution
should be taken when pushing. These issues are discussed below.
|
