<div dir="ltr">FYI, I have tested out using a gerrit style "commit --amend" and "push -f", and how github seems to know when reviewed changes have been fixed.<div><br></div><div>Try it out.</div><div><br></div><div>- Luis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 13, 2017 at 12:43 PM, Michael Adam <span dir="ltr"><<a href="mailto:obnox@samba.org" target="_blank">obnox@samba.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2017-03-10 at 00:48 -0500, Luis Pabon wrote:<br>
> Hi Michael,<br>
> As our git guru, do you mind proposing a workflow for Heketi using<br>
> Github. I'm so tired of not knowing if I'm doing the correct thing with<br>
> the Github UI. I remember you and José mentioned to squash and force push<br>
> to the feature branch.<br>
> I can't seem to find a good workflow on the net. Do you mind putting a<br>
> workflow together that would help us not mess up the git log anymore?<br>
<br>
</span>Hi Luis,<br>
<br>
well, not sure I'm a git guru, but coming from mostly<br>
doing git on the command line, I may be a little special.<br>
<span class=""><br>
> Thanks, and sorry for being a pain about that before :)<br>
<br>
</span>Well, it's not about you or someone else doing it wrong<br>
necessarily, but some of those github workflows just<br>
confuse me. And yes, I do have some ideas about how a git<br>
tree should ideally look like. And sorry for being<br>
a pain about that before... ;-)<br>
<br>
I can certainly try and write up what's on my mind here.<br>
We can then discuss it.<br>
<br>
Cheers - Michael<br>
</blockquote></div><br></div>