[
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073529#comment-15073529
]
ASF GitHub Bot commented on EAGLE-84:
-------------------------------------
Github user anyway1021 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/42#issuecomment-167723365
Sure, Hao, that's a good suggestion and the old name was not defined as the
final one, i'll change these things and add commits to the PR.
On Tue, Dec 29, 2015 at 11:57 AM, Hao Chen <notificati...@github.com> wrote:
> And how do you think rename to script to a more meaningful name say
> merge_pull_request.py instead of auto_merge.py? Because the script is
> actually executed manually but not automatically.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/incubator-eagle/pull/42#issuecomment-167714742>
> .
>
> Create scripts for merging PRs automatically
> --------------------------------------------
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
> Issue Type: Task
> Reporter: Michael Wu
> Assignee: Hao Chen
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as
> good-to-merge, people are willing to merge it with scripts to go through
> necessary steps automatically, and can form the message of final aggregated
> commit in a unified format. To achieve this, we are attempted to create the
> script.
> As discussed, the format of message should be like below (ignore the lines
> consisted of asterisks):
> **********************************************
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **********************************************
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
