+ [2016-11-17T23:38:41Z] tobiasvl you should fork the repo and clone that
+ [2016-11-17T23:40:32Z] tetsuo55 so there is no way around that requirement
+ [2016-11-17T23:40:48Z] tobiasvl no, the remote github repo can't pull from your local machine

message no. 156899

Posted by spal in #github at 2016-11-17T15:02:24Z

okay. thanks. I am wondering why https://help.github.com/articles/syncing-a-fork/ suggests the three command approach (git fetch upstream; git checkout master; git merge upstream/master). Is there any advantage in using these three commands instead of my shortened two commands?
+ [2016-11-18T03:56:06Z] BlueProtoman I have a Git repo. Its primary remote (origin) is on a machine at my university, but I want to manage it with GitHub so my team and I can do our primary work there (issue tracking, pull requests, etc.). What's a good fire-and-forget way to mirror it?
+ [2016-11-18T04:54:57Z] preaction BlueProtoman: create the repo on github, and when it tells you the "clone url": git remote add github <clone url>; git push --mirror github;
+ [2016-11-18T08:57:11Z] mithril My win8 in office have some problem, so I fresh reinstall a win 7. I backup the original ~/.ssh folder, and paste to the user home on win 7.
+ [2016-11-18T08:57:18Z] mithril But I find git-bash do not use the key: when I push a commit in a project, it ask me to input Github Username and Password.
+ [2016-11-18T08:57:47Z] mithril Then I try: eval `ssh-agent -s` , ssh-add ~/.ssh/id_rsa