<div dir="ltr">Hi,<br><div><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 21, 2013 at 5:03 AM, Nathan Woodrow <span dir="ltr"><<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Thanks Larry. Just to note that there are a few shortcuts that one can take that I didn't have in my work follow, things like git rebase -i master rather then giving it the commit. I didn't do this in the blog post in order to show the logic of rebasing onto a commit. If people have better cleaner ways to work then I'm happy to update the post. <div>
<br></div><div>I would also like to see a <span style="font-size:13px;font-family:arial,sans-serif">CONTRIBUTING file made, happy to make a start on that if anyone wants me to. Even if it's just my git stuff then we can add stuff later.</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"></span></div></div></blockquote><div><br></div><div>+1 for starting <span style="font-size:13px;font-family:arial,sans-serif">CONTRIBUTING</span> right now and adding to it as needed. It will hopefully help ensure pull requests are set up, ready to merge. Good for the requester and the commit access devs having to look over lots of requests.<br>
<br></div><div>Would also be good to discuss, for the requester's benefit, how to manage a feature branch in an ongoing pull request. For example, it is common for the requester's github branch to become outdated, no longer capable of being auto-merged by <a href="http://github.com">github.com</a>. Luckily, the pull request feature at <a href="http://github.com">github.com</a> works off of that branch in a 'live' fashion, i.e. the requester can pull qgis upstream master branch into theirs as a rebase and do a 'force push' back up to their github repo. The pull request will then show the branch as viable for auto-merging again.<br>
<br></div><div>Here's what I do in this regard (on my feature branch):<br> git rebase -i HEAD~2<br></div><div> (2 being 2 commits back to rebase)<br></div><div><br>Then, after finishing rebase:<br> git push -f origin HEAD<br>
</div><div> (where 'origin' is the remote name for my <a href="http://github.com">github.com</a> forked repo of QGIS)<br></div><div><br></div><div>Obviously there are potential issues with doing a force push (if others have already pulled it), but it helps in this scenario when the feature branch is more than likely a dead end development branch, to be abandoned or deleted after the merge into master. Those devs testing the requester's branch can always pull to a new local branch after the requester force pushes.<br>
<br></div><div>The benefit of this approach is that the pull request stays the same, with all request comments (not sure about per line comments, though), and the eventual commit(s) are more concise. Process should be tested for any flaws before writing anything up, though.<br>
<br></div><div>Or, we can recommend always creating a new pull request in the case of a requester's feature branch needing rebased again.<br><br></div><div>Another issue is 3-way merges. When asking a requester to rebase their branch via pulling from master, the project is relying upon that individual to properly 3-way merge any conflicts (potentially messing it up and deleting parts of other, previously committed code). Not sure the best approach there, other than carefully going over any pull request that has been subsequently rebased.<br>
<br></div><div>Lastly, we might want to consider disallowing merge commits in pull requests. Requiring only clean, rebased commits on top of current master, or at least merge-able into master.<br></div><div><br></div><div>
Regards,<br></div><div><br></div><div>Larry<br></div><div><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><span style="font-size:13px;font-family:arial,sans-serif">- Nathan</span></div>
</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Feb 21, 2013 at 6:23 AM, Larry Shaffer <span dir="ltr"><<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Hi Amit,<br><div class="gmail_extra"><br><div class="gmail_quote"><div>On Wed, Feb 20, 2013 at 12:48 PM, Amit Kulkarni <span dir="ltr"><<a href="mailto:amitkulz@gmail.com" target="_blank">amitkulz@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br><br>Is there a good document on the git pull workflow that you follow? Is it instead ok to submit git diff against <a href="http://github.com/qgis/Quantum-GIS/" target="_blank">http://github.com/qgis/Quantum-GIS/</a> ?<br>
</blockquote><div><br></div></div><div>Recently, Nathan wrote up a very nice git workflow for QGIS [0]. IMHO, it should be included as a 'best practice' workflow in CODING, or maybe a new document named CONTRIBUTING, in the QGIS source distribution, as a reference for people looking to contribute.<br>
</div><div><br></div><div>Regards,<br><br></div><div>Larry<br><br>[0] <a href="http://nathanw.net/2013/02/05/my-qgis-git-workflow/" target="_blank">http://nathanw.net/2013/02/05/my-qgis-git-workflow/</a><br></div><div><br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thanks<br>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br></blockquote></div><br></div></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br> <br></div></div></div>