[Qgis-community-team] Documentation process

Yves Jacolin yjacolin at free.fr
Thu Jun 23 00:27:12 PDT 2016


Hello,

On Thursday, June 23, 2016 9:20:31 matteo wrote:
> Hi all,
> maybe the suggestions come from yesterday and the caos I did.. :)
Well, as I said in the ticket another build break  occurs yesterday. This is 
something that can occurs, even for typos.

But my workflow is not only for this kind of small issue, it is a good way to 
create a dynamic, interac with people, correct typos in the PR, make sur we 
follow the guidelines, get some suggestion.

I am using this workflow with delazj and this is really great to get such 
valuable feeback.

> well, Yves, do you suggest the following workflow?
> 
> * fork the project
> * create a branch for the feature
> * make changes locally on the created branch
> * push back to the forked repo
> * create a pull request from the new branch and the master one of the
> "original" repo

Yes, it is what I meant, just add 2 last steps:
* make a review of another PR
* wait for a +1 before merging.
 
> could it be a reasonable worflow?
> 
> finally I think, as Alexandre said, that for small changes (e.g. a typo)
> one can directly work on the main repo.. or do you suggest to make other
> branches?
Yes for typo it should be straighforward. We should be pragmatic!

Y.


More information about the Qgis-community-team mailing list