[ 
https://issues.apache.org/jira/browse/CASSANDRA-18372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706357#comment-17706357
 ] 

Brandon Williams commented on CASSANDRA-18372:
----------------------------------------------

I committed this to all the branches, but saw this during commit:

{noformat}
remote: Saw GitHub meta-data in .asf.yaml, but not in main/master/trunk or 
default branch, not updating...
remote: [NOTICE] Notification scheme settings can only be applied to the 
main/master/trunk or default branch.
{noformat}

Indeed, the docs say: 

bq. NOTE: Repository defaults via .asf.yaml may only be set in the 
main/master/trunk or default branch of a repository

so I'll remove the .asf.yaml from the other branches.

> 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]

Reply via email to