+[2019-09-17T17:44:15Z]jlkhttps://developer.github.com/v3/apps/permissions/#permission-on-issues +[2019-09-17T17:45:01Z]flipchanyeah, write POST /repos/:owner/:repo/issues (:write) +[2019-09-17T19:21:55Z]flipchanis there a certain timezone that should be used for https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/ +[2019-09-17T20:13:04Z]flipchannm +[2019-09-17T20:13:10Z]flipchansolved it
create directly the new way instead of polluting my history ?
+[2019-09-18T20:45:29Z]oldandwisehow can we tell when did a git branch was pushed to remote? +[2019-09-18T21:24:34Z]jlkThat isn't really recorded in git metadata +[2019-09-18T21:36:55Z]darkfreewaySo when someone opens a Pull Request, they still can work on that branch and still push into that branch, which is automatically reflected in the Pull Request. +[2019-09-18T21:37:48Z]darkfreewayThis kinda creates a race condition with a reviewer and the developer. Let's say reviewer wants to merge it, and spends some time reviewing the Pull Request. +[2019-09-18T21:39:00Z]darkfreewayAnd when everything looks good, merges the Pull Request, but a developer who now wants to work on a different feature on the same branch, pushed new changes right before reviewer merged.