Perhaps somebody could summarise the tradeoffs? I’m a little concerned about how it would work for our multi-branch workflow. Would we open multiple PRs?
Could we easily link with external CircleCI? It occurs to me, in JIRA proposal mode, that an extra required field for a permalink to GitHub for the patch would save a lot of time I spend hunting for a branch in the comments. > On 12 Dec 2018, at 19:20, jay.zhu...@yahoo.com.INVALID wrote: > > It was discussed 1 year's ago: > https://www.mail-archive.com/dev@cassandra.apache.org/msg11810.html > As all Apache projects are moving to gitbox: > https://reference.apache.org/committer/github, should we revisit that and > change our review/commit process to use github PR?A good example is > Spark:"Changes to Spark source code are proposed, reviewed and committed via > Github pull requests" (https://spark.apache.org/contributing.html). > /jay --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
