[ https://issues.apache.org/jira/browse/METRON-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496693#comment-16496693 ]
ASF GitHub Bot commented on METRON-1590: ---------------------------------------- Github user justinleet commented on the issue: https://github.com/apache/metron/pull/1041 @ottobackwards I think the main thing there would be to do something like this instead of the rm: https://github.com/apache/metron/blob/master/dev-utilities/committer-utils/prepare-commit#L100-L107 I wouldn't really want to do a whole lot more refactoring in this PR, just because it's a pretty minor change. > validate-jira-for-release script checks out project into current directory > not workdir > -------------------------------------------------------------------------------------- > > Key: METRON-1590 > URL: https://issues.apache.org/jira/browse/METRON-1590 > Project: Metron > Issue Type: Bug > Reporter: Justin Leet > Assignee: Justin Leet > Priority: Major > > validate-jira-for-release at > [https://github.com/apache/metron/blob/master/dev-utilities/release-utils/validate-jira-for-release#L165-L168] > The clone checks out into current dir, so `$WORKDIR/metron-$VERSION` never > gets created. However, since the `cd` fails, we stay in the working dir, and > the script happens to work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)