sounds good to me!
thanks for all the effort Yves
Cheers
Matteo
___
Qgis-community-team mailing list for organizing community resources such as
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listin
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
Hi all,
maybe the suggestions come from yesterday and the caos I did.. :)
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 branc
Hi Yves!
I. Think that's a good process, principally for big changes. I see no need
for it for small fixes, as it will slow down documentation writing. But I
am ok if we decide to do it that way and I will follow that guidelines.
Alex Neto
A qui, 23/06/2016, 02:16, Yves Jacolin escreveu:
> Hel
Hello doc contributor,
Currently for each issue or changes in documentation I am using a PR process.
That's mean that I always create a branch and a Pull Request to let other
contributor to comment my contribution.
This way I can let other contributor know my changes and get some feedback
abou
