[
https://issues.apache.org/jira/browse/CASSANDRA-18372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706302#comment-17706302
]
Brandon Williams commented on CASSANDRA-18372:
----------------------------------------------
I guess my question now is, why not all the branches? It seems weird to have
different behavior in other branches. The reason we don't have a .asf.yaml in
older branches is we fixed CASSANDRA-17419 during 4.1-alpha when it was trunk,
but I don't see any reason all of this can't go everywhere.
> A link to the pull request can be attached to the JIRA issue as soon as the
> PR is raised
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18372
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18372
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Maxim Muzafarov
> Assignee: Maxim Muzafarov
> Priority: Normal
> Fix For: 4.1.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> According to the ASF recommendations [1] a link to a pull request might be
> automatically attached to the corresponding JIRA issue if the pull request
> matches the following title: "CASSANDRA-XXXX Something to improve".
> To achieve this, the {{.asf.yml}} must be updated as follows:
> {code}
> notifications:
> ...
> jira_options: link worklog
> {code}
> [1]
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
