[GNC-dev] Git Questions With Documentation

[Geert Janssens]

David,

Considering David T's expressed concern regarding git, setting up 
collaboration in one repo is probably the least complicated. That would allow 
you to help out with the more subtle git operations, and allow David T. to 
worry less about that part.

Geert

Op dinsdag 18 september 2018 15:28:14 CEST schreef David Cousens:
> Thanks Geert,
> 
> I have so far been able to clone David Ts PR into a local copy  on my
> computer. That is not convenient though as it isnt configured as a server
> and has an ISP allocated IP address which changes each time I login.
> 
> I have been looking at the ways github can be used for collaboration.
> 
> > > One other way to do it may be to create the bug branch for the doc
> > > update
> > > in the main Gnucash repository if John and Geert are willing to do that.
> > 
> > I prefer not to and I don't really see the need. There are other ways to
> > collaborate.
> 
> I didn't really think this was a good idea.
> 
> > There is not really anything special about the Gnucash/gnucash-docs repo.
> > What you can do there, you can equally do with your personal forks.
> > 
> > And for that you even don't need to fork David T's repo. You can still
> > pull
> > requests against it from your current Gnucash/gnucash-docs fork.
> > 
> >  You would do
> > 
> > so like any other pull request. The difference is that instead of going
> > with the defaults proposed by github, you change the target repo to David
> > T's repo (sunfish62).
> > 
> > You can publish your changes to your own fork and David T. can look at
> > them
> > there. Or you create PR's and then David T. can review them as part of his
> > builds.
> 
> OK will investigate doing this. I'm OK with git for simple things between a
> local repo and a github repo. I'll just have to explore pulling DavidT's
> changes from his repo and doing PR's to it.
> > Yet another method could be that one of you adds the other as collaborator
> > to your personal fork. In that case both of you can work directly on the
> > same repo.
> > 
> > Regardless of the chosen route, be aware this will require more than basic
> > understanding of how git works. You'll now be on the pulling end of a pull
> > request, which means git's merge mechanics need to be understood.
> 
> Always something new to learn. I have been exploring git in more detail
> lately so time to dig deeper.
> > Regards,
> > 
> > Geert