You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/19 17:37:00 UTC
[jira] [Commented] (METRON-1413) Add Metron Commit Tool
[ https://issues.apache.org/jira/browse/METRON-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332590#comment-16332590 ]
ASF GitHub Bot commented on METRON-1413:
----------------------------------------
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/902
METRON-1413 Add Metron Commit Tool
This PR contributes the `prepare-merge` tool that many (some?) contributors use back to the project itself. Up until now, it has been managed in a separate repo.
I didn't have a logical place to put this tool, so I had to reorganize a bit. Since our tooling has been growing, a reorganization shouldn't be too unexpected.
* Creates top level directory called `metron-dev-support`.
* Moves existing `build_utils` to `metron-dev-support/build-utils`
* Moves existing `build_utils/release-utils` to `metron-dev-support/release-utils`
* Creates `metron-dev-support/committer-utils`
* Adds the `prepare-commit` script to `committer-utils`.
It is a bit easier to see by just looking at it.
```
metron-dev-support/
├── build-utils
│ ├── README.md
│ ├── create_bundled_licenses.sh
│ ├── generate_license.py
│ ├── list_dependencies.sh
│ ├── verify_license.py
│ └── verify_licenses.sh
├── committer-utils
│ ├── README.md
│ └── prepare-commit
└── release-utils
├── metron-rc-check
└── validate-jira-for-release
3 directories, 10 files
```
## Pull Request Checklist
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/metron METRON-1413
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/902.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #902
----
commit 44494212f1fd78e212d15a72f142c9b7534b46f8
Author: Nick Allen <ni...@...>
Date: 2018-01-19T17:28:42Z
METRON-1413 Add Metron Commit Tool
----
> Add Metron Commit Tool
> ----------------------
>
> Key: METRON-1413
> URL: https://issues.apache.org/jira/browse/METRON-1413
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> Contribute the `prepare-merge` tool that many (some?) contributors back to the project itself. Up until now, it has been managed in a separate repo.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)