Re: Proposal to deploy GitLab on

On Wed, 2017-05-17 at 16:47 +0200, Jehan Pagès wrote:
IMO this is a completely broken and over-complicated workflow. For
long term contributors, having their own remote can be
But for one-time contribs?

One-time contributions can be done entirely in the web UI, for example:

1. find the file in the source code you want to modify
2. click the "edit" button
3. "You don't have permission to edit this file. Try forking this
project to edit the file." -> click the "fork" button
4. you get presented with a web-based editor for the file you wanted to
edit, in your fork, do your changes, write a commit message, click
"commit changes"
5. this **automatically** opens a form to create a merge request, you
can just submit it

For one-time contributions, this is a **much** simpler workflow than
cloning the repository, making the changes, committing the change,
making a patch, then sending the patch by email/bugzilla. It even
enables non-technical people to contribute!

And if I send you a patch, you might find it easier to test it locally.
But that completely bypasses your pre-merge CI.

With a pull-request, your CI can run **before** merging any change,
which means you can try and keep master always building and with
passing tests.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]