+ [2019-09-17T17:44:15Z] jlk https://developer.github.com/v3/apps/permissions/#permission-on-issues
+ [2019-09-17T17:45:01Z] flipchan yeah, write POST /repos/:owner/:repo/issues (:write)
+ [2019-09-17T19:21:55Z] flipchan is 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:10Z] flipchan solved it

message no. 174594

Posted by tshirtman in #github at 2019-09-17T13:15:08Z

so every time i want to add actions to a project, i apparently need to first create a workflow the old way, and i need to merge that, and then when i edit this workflow again, i get the button to upgrade to the new system, and i need to remove the workflow i just created and i knew i didn't need to create, then i can add the new files because it's now looking for them. Is there a clean way to
+ [2019-09-18T20:45:29Z] oldandwise how can we tell when did a git branch was pushed to remote?
+ [2019-09-18T21:24:34Z] jlk That isn't really recorded in git metadata
+ [2019-09-18T21:36:55Z] darkfreeway So 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] darkfreeway This 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] darkfreeway And 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.