[
https://issues.apache.org/jira/browse/CASSANDRA-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503167#comment-17503167
]
Michael Semb Wever commented on CASSANDRA-17419:
------------------------------------------------
Patch updated, best we can do here is disable squash and merge, while leaving
rebase enabled. Works for me, as squash and merge are more obvious wrong for
us…
What do others thing? Still an improvement on the status-quo?
> 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
>
> Attachments: Screenshot 2022-03-07 at 17.45.22.png
>
>
> The cassandra project (currently) does not permit commits to be pushed to the
> cassandra repository (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, see
> [here|https://github.com/apache/cassandra-website/blob/trunk/.asf.yaml#L6-L10].
> 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
