+[2015-03-24T20:27:54Z]frymasterpersonally, I'd fork the offical one on github, then clone your fork locally, then add the original as another remote (say, "upstream"). push/pull from your own most of the time, but every now and again to a "pull upstream" and bring in their changes +[2015-03-24T20:28:57Z]codydhfrymaster: That makes a ton of sense. Thanks much!! +[2015-03-24T20:49:30Z]gitinfocodydh: [!fork_sync] You can read a nice guide on how to update your fork with the upstream repository here: https://help.github.com/articles/syncing-a-fork +[2015-03-24T20:49:29Z]VxJasonxVcodydh: !sync +[2015-03-24T20:50:07Z]codydhVxJasonxV: Ah cool, that's good to know.. thank you!
That will redirect your domain to "myuser.github.io/myRepo"
+[2015-03-25T00:14:03Z]p3limWhat scopes are required to read and write comments on commits? +[2015-03-25T00:14:11Z]p3limFor any repo, not just the ones you own +[2015-03-25T00:51:15Z]VxJasonxVp3lim: public repositories? no scope +[2015-03-25T00:51:18Z]VxJasonxVprivate ones? repo scope +[2015-03-25T00:51:23Z]VxJasonxVoh, write comments. ummm