Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can add files using <code>git add</code>, example <code>git add README</code>, <code>git add &lt;folder&gt;/*</code>, or even <code>git add *</code></p> <p>Then use <code>git commit -m "&lt;Message&gt;"</code> to commit files</p> <p>Finally <code>git push -u origin master</code> to push files.</p> <p>When you make modifications run <code>git status</code> which gives you the list of files modified, add them using <code>git add *</code> for everything or you can specify each file individually, then <code>git commit -m &lt;message&gt;</code> and finally, <code>git push -u origin master</code></p> <p>Example - say you created a file README, running <code>git status</code> gives you</p> <pre><code>$ git status # On branch master # Untracked files: # (use "git add &lt;file&gt;..." to include in what will be committed) # # README </code></pre> <p>Run <code>git add README</code>, the files are staged for committing. Then run <code>git status</code> again, it should give you - the files have been added and ready for committing.</p> <pre><code>$ git status # On branch master # Changes to be committed: # (use "git reset HEAD &lt;file&gt;..." to unstage) # # new file: README # nothing added to commit but untracked files present (use "git add" to track) </code></pre> <p>Then run <code>git commit -m 'Added README'</code></p> <pre><code>$ git commit -m 'Added README' [master 6402a2e] Added README 0 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 README </code></pre> <p>Finally, <code>git push -u origin master</code> to push the remote branch <code>master</code> for the repository <code>origin</code>.</p> <pre><code>$ git push -u origin master Counting objects: 4, done. Delta compression using up to 2 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 267 bytes, done. Total 3 (delta 1), reused 0 (delta 0) To xxx@xxx.com:xxx/xxx.git 292c57a..6402a2e master -&gt; master Branch master set up to track remote branch master from origin. </code></pre> <p>The files have been pushed successfully to the remote repository.</p> <p>Running a <code>git pull origin master</code> to ensure you have absorbed any upstream changes</p> <pre><code>$ git pull origin master remote: Counting objects: 12, done. remote: Compressing objects: 100% (4/4), done. remote: Total 8 (delta 4), reused 7 (delta 3) Unpacking objects: 100% (8/8), done. From xxx.com:xxx/xxx * branch master -&gt; FETCH_HEAD Updating e0ef362..6402a2e Fast-forward public/javascript/xxx.js | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) create mode 100644 README </code></pre> <p>If you do not want to merge the upstream changes with your local repository, run <code>git fetch</code> to fetch the changes and then <code>git merge</code> to merge the changes. <code>git pull</code> is just a combination of <code>fetch</code> and <code>merge</code>.</p> <p>I have personally used gitimmersion - <a href="http://gitimmersion.com/" rel="noreferrer">http://gitimmersion.com/</a> to get upto curve on git, its a step-by-step guide, if you need some documentation and help</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload