[GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

Hi Panos, all,

On Sat, May 18, 2019 at 5:59 PM Panagiotis Mavrogiorgos
<pmav99 at gmail.com> wrote:
>
> hello Markus,
>
> I would suggest that:
>
> - even core devs fork the main repo
> - "origin" is the personal remote GRASS repository (e.g. in my case https://github.com/pmav99/grass)
> - everyone adds the main GRASS repository as a secondary remote (e.g. "upstream")

yes, it sounds good to me (while my opinion only counts 0.02 cents here).

> This way:
>
> 1. You always push to "origin" and you create a Pull Request from the Github UI
> 2. To get updates you always pull from "upstream"
> 3. You always rebase your code to "upstream/master".
> 4. You don't need separate instructions for non core-devs.

Updated in a similar way to

https://trac.osgeo.org/grass/wiki/HowToGit#Workflowforcoredevelopers

> Just my 2 cents.

For fetching the updates, is this enough:

git pull --all
?

Thanks for your recommendations,

Markus