[LRUG] [Workflow] Getting a Pull Request from creation to merge

[Matthew Rudy Jacobs]

Thanks everyone for your experience and suggestions.

Something we've implemented this week is having a daily "merge face"
who takes ownership of getting PRs merged, and code deployed to Production.
(we continuously deploy to QA already)

Pairing is something we'd like to do, but haven't got it down yet
(also we have only got 3 devs on the core app, so there'd always be one dev
on their own)

We've got our retrospective on Friday,
so we'll see what takeaways we have ongoing from this.

Thanks all.

On 21 August 2013 05:46, Mark Burns <markthedeveloper at gmail.com> wrote:

> It's a bit of an avoid the question type of answer, but we tend to have a
> rule that pull requests are only
> for work that hasn't been paired on.
>
> Pairing mitigates the issues of context switching, blocking, interrupting,
> etc.
> It also improves team-wide communication, understanding of any of these
> types of process ideas,
> understanding of coding standards or evolving design patterns, sharing
> nifty command-line tricks or
> text-editor wizardry, and general camaraderie.
> Design patterns, or even proposed or evolving design patterns are the
> hardest ideas to communicate
> via either the code itself or comments....
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130821/17a6080a/attachment-0003.html>