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

Michael Semb Wever commented on CASSANDRA-17419:
------------------------------------------------

bq. Confused here. Does it currently allow it and this patch / ticket are about 
disabling it?

erh, bad writing… 

should say: " The cassandra project (currently) does not permit commits to be 
pushed to the cassandra repository (trunk or any branch) via GH pull requests."

> Prevent GH pull request commits to cassandra repository
> -------------------------------------------------------
>
>                 Key: CASSANDRA-17419
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17419
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.11.x, 4.0.x, 4.x
>
>
> The cassandra repository (currently) does not allow commits to be pushed to 
> trunk (or any branch) via GH pull requests. It is easy to disable this with a 
> {{.asf.yml}} file.
> Note, our other repositories: cassandra-dtest, cassandra-builds, 
> cassandra-website, cassandra-in-jvm-dtest-api, …; may be candidates for 
> allowing rebased GH PR merges. 
> The cassandra-website repository is already set up to permit these. So long 
> as part of the PR review process tis checking the commit message is of the 
> correct project format it works well (there are no forward merges across 
> projects in this repository).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to