[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [katello-devel] Commit/Review ideas

On 05/22/2012 05:17 PM, Partha Aji wrote:
----- Original Message -----
From: "Og Maciel"<omaciel redhat com>
To: "Jordan OMara"<jomara redhat com>
Cc: katello-devel redhat com
Sent: Tuesday, May 22, 2012 4:59:23 PM
Subject: Re: [katello-devel] Commit/Review ideas

----- Original Message -----
From: "Jordan OMara"<jomara redhat com>
As a reviewer, how do I get notified when you've updated code? How
I see your progress over time?

Github does not have a workflow for this, so I'd say stick to
"commit/pull request often" as best practice :)
Og Maciel

Senior QA Engineer
Red Hat, Inc.
irc: omaciel

katello-devel mailing list
katello-devel redhat com

I like Eric's "create a remote feature branch in upstream and then do pull requests to that before another pull request to master from there" approach to deal with your "how do I get notified" issue.

I agree.. it seems like they are using pull requests as branches.

-- bk

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]