[llvm-dev] Allowing PRs on GitHub for some subprojects (original) (raw)

Mehdi AMINI via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 20 10:42:14 PST 2020


Hi,

This was part of what I proposed when we integrated MLIR in LLVM ( http://lists.llvm.org/pipermail/llvm-dev/2019-November/136579.html ), we were already using pull-requests before and had CI infrastructure already built for it. Ultimately we didn't press this further, divergence inside the repo / between the subproject does not seems desirable in my opinion:

So in summary: I'd rather find a path for the full-project to do this, but acknowledging that there are few blockers to solve before getting there (cf other threads on the topic).

-- Mehdi

On Thu, Feb 20, 2020 at 10:21 AM Louis Dionne via llvm-dev < llvm-dev at lists.llvm.org> wrote:

Hi,

I know there has been significant discussion about "moving" from Phabricator to GitHub reviews and pull requests, etc. I'm not suggesting that we do anything in terms of global LLVM policy. However, as a maintainer of libc++, I commit a lot of other people's code for them. It would be a huge time saver for me if I could nicely suggest to contributors (not force them) to use PRs instead of Phabricator for their contributions. It would also handle commit attribution properly, which is a pain right now. Would it be possible to allow GitHub PRs to be submitted on the monorepo so as to let individual sub-projects deal with it however they please? I've spoken to numerous people involved in libc++ development and they would like to start submitting PRs (and for the others, we'll still accept Phabricator reviews). Perhaps it is possible to setup some kind of filter such that PRs touching only libcxx/ and libcxxabi/ can be submitted, but otherwise they're closed by the bot? Cheers, Louis


LLVM Developers mailing list llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200220/3b81d74f/attachment.html>



More information about the llvm-dev mailing list