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

Vaclav Petras wenzeslaus at gmail.com
Thu May 16 06:16:32 PDT 2019


On Thu, May 16, 2019 at 8:26 AM Bas Couwenberg <sebastic at xs4all.nl> wrote:
>
> On 2019-05-16 14:16, Markus Neteler wrote:
> > #### External contributors
> > # workflow for external contributors - they have to fork the repo in
> > GitHub Web interface
> > # create fork via github GUI
> > git clone $my_for_url
> > # all steps see above
> > ...
> > # push feature branch to own fork repo of GRASS GIS
> > git push origin $feature_branch_name   # here: origin is fork repo
> > # create pull request in GitHub Web interface (the link is shown in
> > the terminal)
>
> May I suggest cloning the grass repo and adding the fork as an
> additional remote, this makes merging changes from the grass repo
> easier.
> ...

+1 for Markus, Carmen, and Bas. That's what I see used elsewhere too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190516/9e600033/attachment.html>


More information about the grass-dev mailing list