After setting up a GitHub account, configure your local repository, using gitbash
Create a folder for your local repository
mkdir /c/localrepo
cd /c/localrepo
mkdir /c/localrepo
cd /c/localrepo
Git localrepo config
git config –global user.name “username”
git config –global user.email “youremail@yourdomain”
git init
git remote add origin https://github.com/username/repository.git
git config –global user.name “username”
git config –global user.email “youremail@yourdomain”
git init
git remote add origin https://github.com/username/repository.git
Copy/Create your file in your local repository and configure it for git
git add File.txt
git commit -m “Add a comment for your addition/update”
git add File.txt
git commit -m “Add a comment for your addition/update”
Push your file from your localrepo to your GitHub repository
git push
warning: push.default is unset; its implicit value has changed in
Git 2.0 from ‘matching’ to ‘simple’. To squelch this message
and maintain the traditional behavior, use:
git push
warning: push.default is unset; its implicit value has changed in
Git 2.0 from ‘matching’ to ‘simple’. To squelch this message
and maintain the traditional behavior, use:
git config –global push.default matching
To squelch this message and adopt the new behavior now, use:
git config –global push.default simple
When push.default is set to ‘matching’, git will push local branches
to the remote branches that already exist with the same name.
to the remote branches that already exist with the same name.
Since Git 2.0, Git defaults to the more conservative ‘simple’
behavior, which only pushes the current branch to the corresponding
remote branch that ‘git pull’ uses to update the current branch.
behavior, which only pushes the current branch to the corresponding
remote branch that ‘git pull’ uses to update the current branch.
See ‘git help config’ and search for ‘push.default’ for further information.
(the ‘simple’ mode was introduced in Git 1.7.11. Use the similar mode
‘current’ instead of ‘simple’ if you sometimes use older versions of Git)
(the ‘simple’ mode was introduced in Git 1.7.11. Use the similar mode
‘current’ instead of ‘simple’ if you sometimes use older versions of Git)
fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use
To push the current branch and set the remote as upstream, use
git push –set-upstream origin master
git config –global push.default simple
git push –set-upstream origin master
git push –set-upstream origin master
Comments
Post a Comment