latest 20 messages by StephenA1

+ [2014-10-21T19:11:44Z] StephenA1 ya read the help. was confused also
+ [2014-10-21T19:09:58Z] StephenA1 The repo it still under my name but in the options in teh Transfer ownership section is says:"This repository is being transferred to xxxxxx”
+ [2014-10-21T19:09:11Z] StephenA1 does the user who you are transfering too have to accept?
+ [2014-10-21T19:09:02Z] StephenA1 Transfering ownership?
+ [2014-10-21T19:08:58Z] StephenA1 When transfering a repo, how long does it take to transfer?
+ [2014-07-24T04:12:04Z] StephenA1 anyone know why the GitHub dataset on Google BigQuery does not contain Issue Details? Only seems to capture the fact that a issue was created or closed, but does not log any of the attributes of that creation such as the title and body field
+ [2014-07-04T07:35:11Z] StephenA1 get it working?
+ [2014-07-04T07:31:52Z] StephenA1 or https://help.github.com/articles/pushing-to-a-remote
+ [2014-07-04T07:31:43Z] StephenA1 try this: http://stackoverflow.com/questions/2765421/push-a-new-local-branch-to-a-remote-git-repo-and-track-it-too
+ [2014-07-04T07:31:11Z] StephenA1 and you have your internal repo
+ [2014-07-04T07:31:02Z] StephenA1 so you did your mirror
+ [2014-07-04T07:30:32Z] StephenA1 branches are upcoming feautes and changes until they are merged into master which means they are “live"
+ [2014-07-04T07:30:05Z] StephenA1 typically my flow is treating master as prod
+ [2014-07-04T07:28:45Z] StephenA1 should be your clone/mirror. Then you branch, update, test, and then merge with master (or whatever your process is)
+ [2014-07-04T07:23:13Z] StephenA1 here is a example of closing issues accross repos: https://github.com/blog/1439-closing-issues-across-repositories