On Sat, Sep 16, 2017 at 8:18 AM David Kaspar [Dee'Kej] <[email protected]> wrote:
> On Fri, Sep 15, 2017 at 5:28 PM, Pavel Valena <[email protected]> wrote: > >> You can do all you want in your fork[1], which Pagure does support. IMHO >> there's no need to use private branches now. >> Pagure also supports PRs[2]. >> > Okay, that's oney way to deal with his. However, making a fork of a > repository where only I maintain it, to later create pull-requests and > accept them myself... Is too much overkill for this kind of workflow. The > only time it would make a sense I guess is when there are multiple > admins/committers working on the package simultaneously. > You don't need to create pull requests at all. git handles multiple remote repositories (the "origin" and your fork) just as easily as it handles one. Saving your work in a separate branch is the same whether that branch is in the main repo or a fork. The only difference is which remote you push to. `git help remote` `git help push`
_______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
