{"id":1660,"date":"2017-02-01T06:34:31","date_gmt":"2017-02-01T06:34:31","guid":{"rendered":"http:\/\/myprojects.advchaweb.com\/?p=1660"},"modified":"2017-02-01T06:34:31","modified_gmt":"2017-02-01T06:34:31","slug":"git-and-git-cola-tutorial","status":"publish","type":"post","link":"https:\/\/myprojects.advchaweb.com\/index.php\/2017\/02\/01\/git-and-git-cola-tutorial\/","title":{"rendered":"Git and Git Cola Tutorial"},"content":{"rendered":"

GIT TUTORIAL
\nref: http:\/\/rogerdudler.github.io\/git-guide\/<\/a>
\n1. Create a new repository
\ncreate a new directory, open it and perform a
\ngit init
\nto create a new git repository.<\/p>\n

2. checkout a repository
\ncreate a working copy of a local repository by running the command
\ngit clone \/path\/to\/repository
\ngit clone https:\/\/github.com\/balanced\/balanced-php.git
\nwhen using a remote server, your command will be
\ngit clone username@host:\/path\/to\/repository
\ngit clone advcha@yahoo.com:https:\/\/github.com\/balanced\/balanced-php.git<\/p>\n

3. workflow
\nyour local repository consists of three “trees” maintained by git. the first one is your “Working Directory” which holds the actual files. the second one is the “Index” which acts as a staging area and finally the “HEAD” which points to the last commit you’ve made.<\/p>\n

4. add & commit
\nYou can propose changes (add it to the Index) using
\ngit add <filename>
\ngit add *
\nThis is the first step in the basic git workflow. To actually commit these changes use
\ngit commit -m “Commit message”
\nNow the file is committed to the HEAD, but not in your remote repository yet.<\/p>\n

5. pushing changes
\nYour changes are now in the “HEAD” of your local working copy. To send those changes to your remote repository, execute
\ngit push origin master
\nChange master to whatever branch you want to push your changes to.<\/p>\n

If you have not cloned an existing repository and want to connect your repository to a remote server, you need to add it with
\ngit remote add origin <server>
\nNow you are able to push your changes to the selected remote server<\/p>\n

6. branching
\nBranches are used to develop features isolated from each other. The master branch is the “default” branch when you create a repository. Use other branches for development and merge them back to the master branch upon completion.<\/p>\n

create a new branch named “feature_x” and switch to it using
\ngit checkout -b feature_x
\nswitch back to master
\ngit checkout master
\nand delete the branch again
\ngit branch -d feature_x
\na branch is not available to others unless you push the branch to your remote repository
\ngit push origin <branch><\/p>\n

7. update & merge
\nto update your local repository to the newest commit, execute
\ngit pull
\nin your working directory to fetch and merge remote changes.
\nto merge another branch into your active branch (e.g. master), use
\ngit merge <branch>
\nin both cases git tries to auto-merge changes. Unfortunately, this is not always possible and results in conflicts. You are responsible to merge those conflicts manually by editing the files shown by git. After changing, you need to mark them as merged with
\ngit add <filename>
\nbefore merging changes, you can also preview them by using
\ngit diff <source_branch> <target_branch><\/p>\n

8. tagging
\nit’s recommended to create tags for software releases. this is a known concept, which also exists in SVN. You can create a new tag named 1.0.0 by executing
\ngit tag 1.0.0 1b2e1d63ff
\nthe 1b2e1d63ff stands for the first 10 characters of the commit id you want to reference with your tag. You can get the commit id by looking at the log<\/p>\n

9. log
\nin its simplest form, you can study repository history using..
\ngit log
\nYou can add a lot of parameters to make the log look like what you want. To see only the commits of a certain author:
\ngit log –author=bob
\nTo see a very compressed log where each commit is one line:
\ngit log –pretty=oneline
\nOr maybe you want to see an ASCII art tree of all the branches, decorated with the names of tags and branches:
\ngit log –graph –oneline –decorate –all
\nSee only which files have changed:
\ngit log –name-status
\nThese are just a few of the possible parameters you can use. For more, see
\ngit log –help<\/p>\n

10. replace local changes
\nIn case you did something wrong, which for sure never happens ;), you can replace local changes using the command
\ngit checkout — <filename>
\nthis replaces the changes in your working tree with the last content in HEAD. Changes already added to the index, as well as new files, will be kept.<\/p>\n

If you instead want to drop all your local changes and commits, fetch the latest history from the server and point your local master branch at it like this
\ngit fetch origin
\ngit reset –hard origin\/master<\/p>\n

11. useful hints
\nbuilt-in git GUI
\ngitk
\nuse colorful git output
\ngit config color.ui true
\nshow log on just one line per commit
\ngit config format.pretty oneline
\nuse interactive adding
\ngit add -i<\/p>\n

GIT COLA
\ntutorial: http:\/\/cerebrux.net\/2013\/02\/07\/github-git-cola-gui-step-by-step-management-of-your-code\/<\/a>
\n1) Install Git Cola GUI through Software Center or through terminal:
\nsudo apt-get install git-cola
\n2) Copy the repository link from the website then Launch Git Cola and paste the link. In terminal, it\u2019s equivalent of
\ngit clone \/github\/repo\/link.git
\nOnce you launch the Git Cola click \u00abClone\u00bb and paste the link you have copied from Github
\nOnce you provided the link, select where to download the repository and click \u00abOpen\u00bb
\nThis is the main window. It\u2019s empty because we haven\u2019t changed any code
\n3) You can edit your preferences by clicking Edit menu were you can customize your settings like email, username, prepared editor etc. In terminal it\u2019s equivalent of:
\ngit config –global user.name ‘John Doe’
\ngit config –global user.email ‘johndoe@mail.com’
\nTo edit your preferences, click on \u00abEdit \u2013> Preferences\u00bb
\n4) Now edit some files inside your local repository clone and the hit the refresh Rescan button on Git Cola. In terminal, it\u2019s equivalent of:
\ngit status
\nand
\ngit diff
\nOpen the file that you need to edit and start editing. Save and close the file
\n5) Now once you can hit Stage, Comment to add a message for the changes and the Commit these changes:
\nIn terminal, it\u2019s equivalent of
\ngit add filename
\ngit add README.md
\nand then
\ngit commit -m ‘Commit message’
\ngit commit -m ‘Update the README file for better description’
\nOR COMBINE ADD AND COMMIT LIKE THIS:
\ngit commit -a -m ‘Update the README file for better description’
\nClick Stage, add some comment and then commit
\n6) You can also Tag your changes to create versions of your repo by clicking Actions menu \u2013> Create Tag
\nIn terminal, it\u2019s equivalent of
\ngit tag -a v4.5.6 -m ‘my version 4.5.6’
\nCreate tag by clicking \u00abActions \u2013> Add Tag\u00bb
\n7) Now you can upload (push) your changes and versions (tags) to your GitHub account.
\nIn terminal, it\u2019s equivalent of
\ngit push origin master
\nand your tag with
\ngit push origin v1.0.4
\nClick on \u00abPush\u00bb on the main window, check that \u00abInclude tags\u00bb is activated and then click Push
\nProvide your Username and Password of your Github account
\nCheck the commands tab to see the background messages
\n8) Now you can go to your Github page to see your changes and your tags
\nRefresh the GitHub page to see your comment and the commit history<\/p>\n

I WANT TO UPDATE MY LOCAL REPOSITORY:
\nref:http:\/\/stackoverflow.com\/questions\/1443210\/updating-a-local-repository-with-changes-from-a-github-repository
\nteddy@teddy-K43SJ:~\/Documents\/java\/processing-java-client$ git pull origin master
\nUsername for ‘https:\/\/github.com’: advcha
\nPassword for ‘https:\/\/advcha@github.com’:
\nFrom https:\/\/github.com\/finix-payments\/processing-java-client
\n* branch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 master\u00a0\u00a0\u00a0\u00a0 -> FETCH_HEAD
\nUpdating 79ff8fe..c52614a
\nerror: Your local changes to the following files would be overwritten by merge:
\nsrc\/main\/java\/com\/finix\/payments\/processing\/client\/Configuration.java
\nsrc\/main\/java\/com\/finix\/payments\/processing\/client\/model\/User.java
\nPlease, commit your changes or stash them before you can merge.
\nAborting
\nref:http:\/\/stackoverflow.com\/questions\/15745045\/how-do-i-resolve-git-saying-commit-your-changes-or-stash-them-before-you-can-me
\nhttps:\/\/git-scm.com\/book\/en\/v1\/Git-Tools-Stashing
\nso pls do:
\ngit stash
\nthen repeat:
\ngit pull origin master<\/p>\n

I ADDED A .gitignore FILE. I ALREADY ADD AND COMMIT THE FILE BUT THEN I GOT ERROR HERE WHEN TRYING TO PUSH A CHANGES:
\n! [rejected]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 master -> master (fetch first)
\nerror: failed to push some refs to ‘https:\/\/github.com\/advcha\/persuratan.git’
\nhint: Updates were rejected because the remote contains work that you do
\nhint: not have locally. This is usually caused by another repository pushing
\nhint: to the same ref. You may want to first integrate the remote changes
\nhint: (e.g., ‘git pull …’) before pushing again.
\nhint: See the ‘Note about fast-forwards’ in ‘git push –help’ for details.
\nSO ACTUALLY I DELETED A FEW FILES (WITH ~) ON THE REMOTE REPO. I NEED TO UPDATE MY LOCAL REPO FIRST
\ngit pull origin master
\nTHEN PUSH AGAIN
\ngit push origin master<\/p>\n

IF WE DONT WANT TO UPLOAD\/PUSH A FILE LIKE database.php
\n1. Create a new file .gitignore
\nhere is the content:
\napp\/config\/database.php
\n2. type: git commit -a -m ‘add .gitignore file’
\n3. type: git push OR git push origin master<\/p>\n

REMOTE, BRANCH, CHECKOUT
\n1. check our remote repo:
\ntype: git remote OR MORE DETAIL git remote -v
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git remote -v
\norigin\u00a0\u00a0 \u00a0https:\/\/github.com\/advcha\/persuratan.git (fetch)
\norigin\u00a0\u00a0 \u00a0https:\/\/github.com\/advcha\/persuratan.git (push)<\/p>\n

2. We can add a branch in the remote repo.
\non the remote repo website, just click the down arrow at Branch:master then type a branch we want like: addfeature<\/p>\n

3. in local repo, check our branch
\ngit branch
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git branch
\n* master
\nWE ONLY HAVE ONE BRANCH ‘master’ YET
\n4. create a local repo:
\ngit branch addfeature
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git branch addfeature
\nTHEN check again:
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git branch
\naddfeature
\n* master
\n5. to switch to the new local repo:
\ngit checkout addfeature
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git checkout addfeature
\nSwitched to branch ‘addfeature’
\n6. make a change in index.html file (AYNTHING) then check status:
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git status
\nOn branch addfeature
\nChanges not staged for commit:
\n(use “git add <file>…” to update what will be committed)
\n(use “git checkout — <file>…” to discard changes in working directory)<\/p>\n

modified:\u00a0\u00a0 index.html<\/p>\n

no changes added to commit (use “git add” and\/or “git commit -a”)
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git commit -a -m ‘change index.php test’
\n[addfeature fc28a68] change index.php test
\n1 file changed, 103 insertions(+), 102 deletions(-)
\nrewrite index.html (97%)
\n7. commit the changes
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git commit -a -m ‘change index.php test’
\n[addfeature fc28a68] change index.php test
\n1 file changed, 103 insertions(+), 102 deletions(-)
\nrewrite index.html (97%)
\n8. then push to the remote repo (branch ‘addfeature’)
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git push addfeature
\n9. Check the remote repo
\nindex.html in master branch not affected ONLY in addfeature branch
\n10. merge the branch to master(NOT WORKING!!!)
\ngit merge master
\ngit checkout master
\ngit push
\nOK THIS HAS TO BE DONE IN github PAGE. FIRST CLICK ‘New Pull Request’
\n11. Click ‘Create Pull Request’ … THEN WE CAN MERGE IT
\nAT LAST WE CAN DELETE THE ‘addfeature’ BRANCH BECAUSE ITS ALREADY MERGED TO ‘master’ BRANCH!
\nWE CAN ALSO DELETE THE REMOTE BRANCH FROM TERMINAL WITH git push origin :addfeature (BE CAREFULL!!!)
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git push origin :addfeature
\nUsername for ‘https:\/\/github.com’: advcha
\nPassword for ‘https:\/\/advcha@github.com’:
\nerror: unable to delete ‘addfeature’: remote ref does not exist
\nerror: failed to push some refs to ‘https:\/\/github.com\/advcha\/persuratan.git’
\nref:http:\/\/makandracards.com\/makandra\/621-git-delete-a-branch-local-or-remote
\nhttp:\/\/stackoverflow.com\/questions\/2003505\/delete-a-git-branch-both-locally-and-remotely
\n12. NOW WE NEED TO MERGE IT ALSO IN OUR LOCAL REPO
\ntype: git checkout master
\nthen: git pull
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git checkout master
\nAlready on ‘master’
\nYour branch is up-to-date with ‘origin\/master’.
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git pull
\nremote: Counting objects: 1, done.
\nremote: Total 1 (delta 0), reused 0 (delta 0), pack-reused 0
\nUnpacking objects: 100% (1\/1), done.
\nFrom https:\/\/github.com\/advcha\/persuratan
\n1d338b5..7cc859e\u00a0 master\u00a0\u00a0\u00a0\u00a0 -> origin\/master
\nUpdating 1d338b5..7cc859e
\nFast-forward
\nindex.html | 187 +++++++++++++++++++++++++++++++——————————
\n1 file changed, 94 insertions(+), 93 deletions(-)
\n13. DELETE LOCAL BRANCH ‘addfeature’ (ref:http:\/\/makandracards.com\/makandra\/621-git-delete-a-branch-local-or-remote)
\ntype: git branch -d addfeature
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git branch -d addfeature
\nDeleted branch addfeature (was fc28a68).
\n14. Check the branch again
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git branch
\n* master
\n15. SYNCHRONIZED THE BRANCHES (REMOTE & LOCAL)
\nteddy@teddy-K43SJ:~\/Documents\/works\/persuratan$ git fetch -p
\nFrom https:\/\/github.com\/advcha\/persuratan
\nx [deleted]\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 (none)\u00a0\u00a0\u00a0\u00a0 -> origin\/addfeature<\/p>\n

MERGE TWO REPOSITORIES
\nre:http:\/\/saintgimp.org\/2013\/01\/22\/merging-two-git-repositories-into-one-repository-without-losing-file-history\/
\nhttp:\/\/stackoverflow.com\/questions\/1425892\/how-do-you-merge-two-git-repositories<\/p>\n

REAL WORLD SAMPLE DEVELOPMENT WITH GITHUB:http:\/\/nvie.com\/posts\/a-successful-git-branching-model\/<\/p>\n

WORKING SAMPLE FROM SCRATCH
\n1. Create a new repository in my github account: OpenCV-python (https:\/\/github.com\/advcha\/OpenCV-Python.git)
\n2. in my terminal, clone it into \/media\/data\/MASTER\/opencv\/
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv$ git clone https:\/\/github.com\/advcha\/OpenCV-Python.git
\nCloning into ‘OpenCV-Python’…
\nremote: Counting objects: 3, done.
\nremote: Compressing objects: 100% (2\/2), done.
\nremote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
\nUnpacking objects: 100% (3\/3), done.
\nChecking connectivity… done.
\n3. Add some files and directories in it like images\/ and opencv_read_write.py (I copied them from \/home\/teddy\/opencv\/samples\/python\/) OR SEARCH THE FILENAME IN \/media\/data\/MASTER\/opencv\/opencv_python_tutorial.txt
\n4. check the un-uploaded file and dir with ‘git status’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git status
\nOn branch master
\nYour branch is up-to-date with ‘origin\/master’.<\/p>\n

Untracked files:
\n(use “git add <file>…” to include in what will be committed)<\/p>\n

images\/
\nopencv_read_write.py<\/p>\n

nothing added to commit but untracked files present (use “git add” to track)
\n5. Add the file and the dir to prepare for uploading with ‘git add *’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git add *<\/p>\n

6. Commit the file and dir and give it a tag ‘upload some python scripts’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git commit -a -m ‘upload some python scripts’
\n[master 46abb81] upload some python scripts
\n28 files changed, 17 insertions(+)
\ncreate mode 100644 images\/Temperate 09 – Small.png
\ncreate mode 100644 images\/Temperate 09 – Small_clean.png
\ncreate mode 100644 images\/approx.jpg
\ncreate mode 100644 images\/bolt.png
\ncreate mode 100644 images\/clahe.jpg
\ncreate mode 100644 images\/dave.jpg
\ncreate mode 100644 images\/dave.png
\ncreate mode 100644 images\/fruits.jpg
\ncreate mode 100644 images\/fruits_gray.jpg
\ncreate mode 100644 images\/grass.png
\ncreate mode 100644 images\/hand.jpg
\ncreate mode 100644 images\/john_dory-zeus_faber.jpg
\ncreate mode 100644 images\/mario.jpg
\ncreate mode 100644 images\/mario_coin.png
\ncreate mode 100644 images\/mario_coin1.png
\ncreate mode 100644 images\/messi5.jpg
\ncreate mode 100644 images\/messi_face.jpg
\ncreate mode 100644 images\/more_coins.png
\ncreate mode 100644 images\/my_family.jpg
\ncreate mode 100644 images\/noisy2.png
\ncreate mode 100644 images\/opencv_logo.png
\ncreate mode 100644 images\/rect.jpg
\ncreate mode 100644 images\/shapes.png
\ncreate mode 100644 images\/star.jpg
\ncreate mode 100644 images\/star2.jpg
\ncreate mode 100644 images\/uss_arizona.jpg
\ncreate mode 100644 images\/water_coins.jpg
\ncreate mode 100644 opencv_read_write.py<\/p>\n

7. Push them to github account with ‘git push origin master’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git push origin master
\nUsername for ‘https:\/\/github.com’: advcha
\nPassword for ‘https:\/\/advcha@github.com’:
\nCounting objects: 32, done.
\nDelta compression using up to 4 threads.
\nCompressing objects: 100% (31\/31), done.
\nWriting objects: 100% (31\/31), 5.93 MiB | 1.10 MiB\/s, done.
\nTotal 31 (delta 0), reused 0 (delta 0)
\nTo https:\/\/github.com\/advcha\/OpenCV-Python.git
\n330ef49..46abb81\u00a0 master -> master<\/p>\n

8. Check again my local repo with ‘git status’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git status
\nOn branch master
\nYour branch is up-to-date with ‘origin\/master’.<\/p>\n

nothing to commit, working directory clean<\/p>\n

OK DONE<\/p>\n

9. Add some python scripts from \/home\/teddy\/opencv\/samples\/python\/ (copy and paste them into \/media\/data\/MASTER\/opencv\/OpenCV-Python)<\/p>\n

10. check with ‘git status’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git status
\nOn branch master
\nYour branch is up-to-date with ‘origin\/master’.<\/p>\n

Untracked files:
\n(use “git add <file>…” to include in what will be committed)<\/p>\n

drawing.py
\nmouse_draw.py
\nmouse_paint.py
\nmouse_paint_img.py<\/p>\n

nothing added to commit but untracked files present (use “git add” to track)<\/p>\n

11. add them with ‘git add *’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git add *<\/p>\n

12. commit them:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git commit -a -m ‘Upload some python scripts’
\n[master 567e4fd] Upload some python scripts
\n4 files changed, 165 insertions(+)
\ncreate mode 100644 drawing.py
\ncreate mode 100644 mouse_draw.py
\ncreate mode 100644 mouse_paint.py
\ncreate mode 100644 mouse_paint_img.py<\/p>\n

13. The last, push them into my github account:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git push origin master
\nUsername for ‘https:\/\/github.com’: advcha
\nPassword for ‘https:\/\/advcha@github.com’:
\nCounting objects: 7, done.
\nDelta compression using up to 4 threads.
\nCompressing objects: 100% (6\/6), done.
\nWriting objects: 100% (6\/6), 2.66 KiB | 0 bytes\/s, done.
\nTotal 6 (delta 0), reused 0 (delta 0)
\nTo https:\/\/github.com\/advcha\/OpenCV-Python.git
\n46abb81..567e4fd\u00a0 master -> master<\/p>\n

OK. DO IT OVER AND OVER AGAIN FOR THE OTHERS FILES AND DIRECTORIES!!!<\/p>\n

HOW TO UPDATE FILE AND UPDATE THE CHANGES TO REMOTE REPO?
\n1. Modify README.md to
\nSome python scripts for practising OpenCV. Use Python 2.7 (some scripts works for Python 3.4) and OpenCV 3.1.0.
\nSAVE THE MODIFICATION\u00a0\u00a0 (IT BETTER TO REMOVE THE TEMPORARY FILE LIKE README.md~)
\n2. check the status:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git status
\nOn branch master
\nYour branch is up-to-date with ‘origin\/master’.<\/p>\n

Changes not staged for commit:
\n(use “git add <file>…” to update what will be committed)
\n(use “git checkout — <file>…” to discard changes in working directory)<\/p>\n

modified:\u00a0\u00a0 README.md<\/p>\n

Untracked files:
\n(use “git add <file>…” to include in what will be committed)<\/p>\n

README.md~<\/p>\n

no changes added to commit (use “git add” and\/or “git commit -a”)
\n3. use ‘git add *’
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git add *
\n4. commit:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git commit -a -m ‘Update README’
\n[master c7ea471] Update README
\n2 files changed, 3 insertions(+), 1 deletion(-)
\ncreate mode 100644 README.md~
\n5. use ‘git push’:
\nteddy@teddy-K43SJ:\/media\/data\/MASTER\/opencv\/OpenCV-Python$ git push origin master
\nUsername for ‘https:\/\/github.com’: advcha
\nPassword for ‘https:\/\/advcha@github.com’:
\nCounting objects: 5, done.
\nDelta compression using up to 4 threads.
\nCompressing objects: 100% (3\/3), done.
\nWriting objects: 100% (3\/3), 367 bytes | 0 bytes\/s, done.
\nTotal 3 (delta 1), reused 0 (delta 0)
\nTo https:\/\/github.com\/advcha\/OpenCV-Python.git
\n1f66fba..c7ea471\u00a0 master -> master<\/p>\n

LOCAL REPO DIRECTORY HAS DIFFERENT NAME WITH REMOTE REPO:
\nref:http:\/\/stackoverflow.com\/questions\/8570636\/change-name-of-folder-when-cloning-from-github
\ngit clone https:\/\/github.com\/sferik\/sign-in-with-twitter.git signin
\nREMOTE REPO: sign-in-with-twitter
\nLOCAL REPO: signin<\/p>\n","protected":false},"excerpt":{"rendered":"

GIT TUTORIAL ref: http:\/\/rogerdudler.github.io\/git-guide\/ 1. Create a new repository create a new directory, open it and perform a git init to create a new git repository. 2. checkout a repository create a working copy of a local repository by running the command git clone \/path\/to\/repository git clone https:\/\/github.com\/balanced\/balanced-php.git when using a remote server, your command … Continue reading “Git and Git Cola Tutorial”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[57],"tags":[],"class_list":["post-1660","post","type-post","status-publish","format-standard","hentry","category-github"],"_links":{"self":[{"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/posts\/1660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/comments?post=1660"}],"version-history":[{"count":1,"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/posts\/1660\/revisions"}],"predecessor-version":[{"id":1661,"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/posts\/1660\/revisions\/1661"}],"wp:attachment":[{"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/media?parent=1660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/categories?post=1660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/myprojects.advchaweb.com\/index.php\/wp-json\/wp\/v2\/tags?post=1660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}