+ [2017-03-20T15:32:49Z] lrochfort Stummi: OK, and then let upstream worry about the merge?
+ [2017-03-20T15:33:18Z] Stummi yeah, thats how I would do it
+ [2017-03-20T15:33:37Z] lrochfort Sounds good. Thanks for the advice.
+ [2017-03-20T16:25:06Z] GodGinrai is there a way to execute a hook pre-merge on github? I want to execute a hook that creates a backup branch of the branch being merged into every time you try to merge a PR using Github's UI
+ [2017-03-20T19:42:15Z] Sasazuka Just enabled 2FA on my github account but I was getting "fatal repo not found" error for a private repo and I had to enable the "repo" scopes for my personal access token - just wondering if that's the correct scope?

message no. 166064

Posted by lrochfort in #github at 2017-03-20T15:31:55Z

Stummi: Thanks. One question. If I have work for a later PR, that changes some of the same files as the previous PR, should I base them on master or my previous PR?
+ [2017-03-21T03:17:21Z] buzzedword im trying to complete an integration authentication following the directions located here: https://developer.github.com/early-access/integrations/authentication/#as-an-integration
+ [2017-03-21T03:18:10Z] buzzedword i dont fully understand what's happening in the example provided where we use the PEM file provided after you create your integration, and generate a private key to use to sign the JWT
+ [2017-03-21T03:19:27Z] buzzedword i dont really work with JWT or OpenSSL that often, so i was under the assumption that the .pem github provides is the key thats needed, but it clearly needs more-- what specifically is being generated in the `OpenSSL::PKey::RSA.new` step in the example?
+ [2017-03-21T03:20:53Z] buzzedword further, reading the ruby stdlib docs, the `new` method generates an "RSA instance" or an "RSA keypair", but again, is unclear as to if its public/private, format, or encoding