[
https://issues.apache.org/jira/browse/SQOOP-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115726#comment-15115726
]
Abraham Fine commented on SQOOP-2799:
-------------------------------------
my workflow follows the current logic.
my suggestion was simply that if the name of the current git branches follows
a certain convention (where we can detect a corresponding jira ticket) the user
would not need to specify the jira ticket via a command line argument when
running the tool.
now that you mention it though, i personally would expect the tool to ignore
staging and only use committed changes. other devs may feel differently.
> Sqoop2: Add custom branch detection to upload-patch.py
> ------------------------------------------------------
>
> Key: SQOOP-2799
> URL: https://issues.apache.org/jira/browse/SQOOP-2799
> Project: Sqoop
> Issue Type: Sub-task
> Affects Versions: 1.99.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
>
> It seems that some devs are using branches for the development using, so it
> might be useful to add detection of this scenario and handle it accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
