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

[Panagiotis Mavrogiorgos]

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")

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.

Just my 2 cents.

P.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190518/323b35e1/attachment.html>