tech-repository archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: irt: Re: Core statement on version control systems



On Sat 29 Nov 2025 at 23:18:04 +0000, David Holland wrote:
> Github pull requests are a fine way to send ten-line patches to random
> projects you aren't part of, provided you've already signed up for
> Github.

I would even claim that the pull request / merge request workflow for
random projects you aren't part of even leaves a lot to be desired. At
least compared to projects where you *are* part of.

When you're part of a project, you can directly clone from the upstream,
make your branch, push it to the upstream repo, and create the pull
request. Any changes that are made upstream are pull-able right away.

If you don't have those permissions, it gets a lot more annoying.  You
must create a fork of the repo on github to your own account. If you
already cloned the repo to your local machine, you now have to switch
its upstream to the fork (or add a new upstream for it). Then you do the
branch + push (to your fork) + pull request dance.

If you just wanted to ever make this one pull request, it stops here.
But if you want to keep following the project, you now have a fork which
gets outdated quickly. Github finally added a button to update a branch
from the original repo, but you'll have to switch though all branches to
keep up to date completely. That can be a lot of work... and even with
the command line I am not aware of a simple way to update the whole repo
(including all branches).

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert                            <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work.           --I. Rose

Attachment: signature.asc
Description: PGP signature



Home | Main Index | Thread Index | Old Index