search for: magit

...more? The way I anticipate doing this: 1. Create fork once for all time 2. Set a remote for the fork in my local clone once for all time while ((I am employed or financially independent) and working on LLVM) 1. Make a commit 2. Push to fork remote 3. Open PR (probably right in emacs using Magit) 4. Respond to comments, push further commits, squash as needed, etc. 5. Declare done and request CI/merge elihw I would never delete the fork or the fork remote. > One exception for me would be docs.  If we could open pull requests - > and possibly the web-edit tool for folks with comm...

On Fri, 10 Jan 2020 at 13:43, Nicolai Hähnle via llvm-dev <llvm-dev at lists.llvm.org> wrote: > It's worth pointing out that GitHub is not able to do this properly, > either. The problem on GitHub's side is that while a pull request can > contain multiple commits, one cannot properly review those commits > individually, and it is not at all possible to approve individual

Hi all, Now that we're on GitHub, we can discuss about pull-requests. I'd like to propose to enable pull-request on GitHub, as a first step as an experimental channel alongside the existing methods for contributing to LLVM. This would allow to find workflow issues and address them, and also LLVM contributors in general to start getting familiar with pull-requests without committing to