2020-04-03 UTC
mauz555, [tantek], KartikPrabhu, gRegorLove_, varun1, [KevinMarks], Sajesajama, Main, [jgmac1106], [LewisCowles], jamietanna, [grantcodes], [Michael_Beckwi], jeremycherfas, IWSlackGateway1, Sajesajama_, [snarfed], [chrisaldrich], [jeremycherfas], gRegorLove, [kimberlyhirsh], [schmarty] and [jacky] joined the channel
# 19:19 gRegorLove I think most of those issues have pending PRs that will close them once merged
# 19:19 GWG I'll see if I can get up to speed.
# 19:19 gRegorLove [schmarty], GWG, any other parser devs, would appreciate review on PRs
# 19:20 [schmarty] i'm not exactly a parser dev but i sling a lot of PHP and I project manage so i might be able to help. :}
# 19:20 GWG If I feel overwhelmed, I can say so
# 19:21 gRegorLove Much appreciated! It's a pretty simple project to install and run the unit tests
# 19:37 gRegorLove I can merge mblaney's and schmarty's PRs, but does it cause problems if we don't merge earlier PRs first?
# 19:47 gRegorLove Is that something we can do through github UI or have to checkout and do it locally?
# 19:48 GWG gRegorLove: I have never tried to rebase in the GUI.
# 19:48 gRegorLove I'll hold off. We should be able to get the others merged soon so can do them sequentially
# 19:53 Zegnat I don’t think git really has any idea of sequence? If the latter one will cause a conflict if merged first, then the earlier one will probably cause a conflict for the latter one?
# 19:55 gRegorLove Not sure, I'm not great with git merges XD. I may be thinking more of commit conflicts.
jamietanna joined the channel
# 20:01 [schmarty] if there is no conflict, and edits are not to the same lines, it is likely that github will apply each PR cleanly, no matter the order.
[Joe_Masilotti], [snarfed], [chrisaldrich], mauz555 and [fluffy] joined the channel