Merging PRs about development HOT 5 CLOSED

I think this is definitely a conversation worth having, but one we should have with the team at large (not just the front-end team).

from development.

Time travel! Almost four months later, I'll add that our Team decided to merge our own pull requests after requiring reviews. This puts the responsibility of getting a PR through on the person who made it, instead of a PR floating in space until someone decides to look at it. It means the Pull Requester has to get Teammates to review and comment so their code gets included.

from development.

Trend setters!! I think this is something we should really be bringing back up, and @ascott1 you're right it should be an org level discussion. Maybe we can schedule a conversation at the next Dev Cop after @virtix is back from leave? Or should we just start an internal issue in D&D?

from development.

Maybe we can schedule a conversation at the next Dev Cop after @virtix is back from leave? Or should we just start an internal issue in D&D?

I'd vote yes to both of these. Maybe start with the issue and set a hard deadline of "we're going to talk about and finalize this at the Dev CoP meeting on xx/xx/xx."

from development.

Opened an internal discussion in the handbook repo, issue 167 (sorry, no links)

from development.