[
https://issues.apache.org/jira/browse/FALCON-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pracheer Agarwal updated FALCON-2232:
-
Description: When we are returning feeds for an extension job, it is being
returned as
[
https://issues.apache.org/jira/browse/FALCON-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pracheer Agarwal updated FALCON-2232:
-
Summary: Check for null feeds in getFeeds() in ExtensionBean (was: Check
for null feeds
Pracheer Agarwal created FALCON-2232:
Summary: Check for null feeds in ExtensionBean
Key: FALCON-2232
URL: https://issues.apache.org/jira/browse/FALCON-2232
Project: Falcon
Issue Type:
I misread it. +1 for this.
On Thu, Dec 29, 2016 at 5:22 PM, Praveen Adlakha wrote:
> I believe we should be doing a rebase rather than pull and making a merge
> commit.
>
> As far as 1 commit per pull request is concerned we should allow multiple
> commits as for
+1
On Thu, Dec 29, 2016 at 4:53 PM, Sandeep Samudrala
wrote:
> Makes sense.
>
> On Thu, Dec 29, 2016 at 3:55 PM, Pallavi Rao
> wrote:
>
> > While creating a PR, we tend to push the local commits as is when we do a
> > git push into the forked repo.
Makes sense.
On Thu, Dec 29, 2016 at 3:55 PM, Pallavi Rao wrote:
> While creating a PR, we tend to push the local commits as is when we do a
> git push into the forked repo. These local commits include lot of merge
> commits, and intermediate commits. This makes it hard
While creating a PR, we tend to push the local commits as is when we do a
git push into the forked repo. These local commits include lot of merge
commits, and intermediate commits. This makes it hard to review, when some
changes have been requested (as the reviewer has to either look at changes