[
https://issues.apache.org/jira/browse/BOOKKEEPER-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260138#comment-15260138
]
Hudson commented on BOOKKEEPER-920:
-----------------------------------
FAILURE: Integrated in bookkeeper-master #1358 (See
[https://builds.apache.org/job/bookkeeper-master/1358/])
BOOKKEEPER-920: Extend bk-merge-pr.py to add more info to Jira ticketâ¦
(sijie: rev d66b9f0b4d27eae59fb9d6e607f24b2e8a0e611a)
* dev/bk-merge-pr.py
> Extend bk-merge-pr.py to add more info to Jira ticket when merging
> ------------------------------------------------------------------
>
> Key: BOOKKEEPER-920
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-920
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Minor
> Fix For: 4.4.0
>
>
> We should add more information to the Jira ticket when merging a github PR.
> Currently, the update on the Jira contains only the author and commit title.
> It would be good to also have:
> * Author
> * Committer
> * Reviewers (Better if we automatically read the '+1' from the PR comments)
>
> In addition, we should add the option to run the tests locally on the merged
> PR before pushing to apache git.
> Recently we had cases of PRs which were fine on their own, but then tests
> started failing after merging into master (because of other commits since),
> even without git merge conflicts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
