<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Ah ok. So it was only removed from their representation of a pull request. It's not ideal as you can see either the comments or the file but not both at the same time but at least both are still available.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 23, 2020, at 13:10, James Y Knight <<a href="mailto:jyknight@google.com" class="">jyknight@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Actually -- you have shown a slightly different issue -- this one is a UI issue. The commit didn't actually get purged from the repository.......yet. You can tell that by going to the commit directly, <a href="https://github.com/pygments/pygments/commit/626154e9498271420b5fddf54910f332d90626a6" class="">https://github.com/pygments/pygments/commit/626154e9498271420b5fddf54910f332d90626a6</a>.<div class=""><br class=""></div><div class="">So the workaround I proposed wouldn't help this at all.</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 23, 2020 at 4:07 PM James Y Knight <<a href="mailto:jyknight@google.com" class="">jyknight@google.com</a>> wrote:<br class=""></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" class=""><div class="">I started to try to write a workaround for this problem using a github action a couple months ago. The idea is to backup up any ref which is force-pushed, so the commits cannot get garbage collected. I tested it a tiny bit, but I didn't get around to testing is whether the action will be appropriately triggered, with an appropriately-powered secret token, in the case of a pull request update from a user who is not a committer in the repository. </div><div class=""><br class=""></div><div class="">(I have the uneasy feeling it will not be, due to security restrictions)<div class=""><div class=""><br class=""></div><div class="">But, we could certainly deploy something like this, as an external hook if a github action doesn't work. IMO that would be a requirement if we switch to Github Pull Requests, so as not to lose any of the old pull-request commit revisions. Ideally, github would just fix this themselves -- but it is within our power to do so if they do not.</div></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 23, 2020 at 3:43 PM Daniel Sanders via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class="">
<br class="">
> On Jan 23, 2020, at 08:37, David Greene via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class="">
> <br class="">
> Hubert Tong <<a href="mailto:hubert.reinterpretcast@gmail.com" target="_blank" class="">hubert.reinterpretcast@gmail.com</a>> writes:<br class="">
> <br class="">
>>> I read this as the refresh being an entirely new GitHub PR. Is that<br class="">
>>> right? Normally I would expect the same PR to be used but the rebase<br class="">
>>> would cause a force-push of the branch which would update the PR with<br class="">
>>> the new commits but might lose comments. It's that later part I'm<br class="">
>>> unsure about. It would seem odd to me to open an entirely new PR due to<br class="">
>>> a rebase/update of commits to respond to review.<br class="">
>>> <br class="">
>> Use of force push damages the ability to retrieve context on older<br class="">
>> comments. I am not sure of the reason for the case I observed, but the<br class="">
>> context vanished within a week in one instance.<br class="">
> <br class="">
> Does "vanish" mean it was completely gone, or just hidden in some way?<br class="">
<br class="">
I can provide a concrete example as I ran into this recently at <a href="https://github.com/pygments/pygments/pull/1361" rel="noreferrer" target="_blank" class="">https://github.com/pygments/pygments/pull/1361</a>. If you scroll down that PR you'll see an entry 'pygments/lexers/asm.py Show resolved' (actually there's two, it doesn't matter which you pick). If you expand that by clicking 'Show Resolved' you'll see a small amount of context along with the reviewers comment. However, if you click the filename to look at the whole file you end up at <a href="https://github.com/pygments/pygments/pull/1361/files/626154e9498271420b5fddf54910f332d90626a6" rel="noreferrer" target="_blank" class="">https://github.com/pygments/pygments/pull/1361/files/626154e9498271420b5fddf54910f332d90626a6</a> which shows 'We went looking everywhere, but couldn’t find those commits.'. GitHub has already removed the previous version of the patch that the review comments referred to. The commit disappeared almost immediately after my force push.<br class="">
<br class="">
> -David<br class="">
> _______________________________________________<br class="">
> LLVM Developers mailing list<br class="">
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
<br class="">
_______________________________________________<br class="">
cfe-dev mailing list<br class="">
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a><br class="">
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class="">
</blockquote></div>
</blockquote></div>
</div></blockquote></div><br class=""></body></html>