Skip to main content
10 events
when toggle format what by license comment
Mar 5, 2020 at 15:14 comment added Angel Cloudwalker For those of you following the instructions, you can then run "git commit" then "git push" to see the fork changes on your forked GitHub repo
Jan 26, 2018 at 4:28 comment added Ryan stackoverflow.com/a/14074925/470749 was helpful to me because I was getting Permission denied (publickey). fatal: Could not read from remote repository. when trying to fetch from Facebook's Github account upstream.
Aug 21, 2017 at 8:57 review Suggested edits
Aug 21, 2017 at 12:31
May 28, 2017 at 13:02 comment added Shobi I have to do it for all branches separately git merge upstream/master, then check out to develop branch and do git merge upstream/develop
Nov 6, 2015 at 15:19 comment added kenny Might be smart to push with --follow-tags: stackoverflow.com/a/26438076/667847
Sep 21, 2015 at 19:38 history edited Peter Mortensen CC BY-SA 3.0
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/GitHub>).
Apr 10, 2015 at 15:48 history edited unor CC BY-SA 3.0
quote markup
Feb 11, 2015 at 22:50 comment added jumpnett @MichaelMcGinnis After merging locally, you would have to push your changes to github. git push origin master
Jan 23, 2015 at 17:38 comment added Michael McGinnis This updates my local fork, but my fork on Github.com still says "43 commits behind". I had to use lobzik's technique to create a pull request for myself to merge the master changes into my Github.com fork.
Oct 21, 2013 at 23:04 history answered jumpnett CC BY-SA 3.0