`follow-file-renames` linkifies "Newer" button even if current file is the latest #4774

// @gamemaker1

Yes, I can confirm this occurs. It could be fixed by adding a check like this:

diff --git a/source/features/follow-file-renames.tsx b/source/features/follow-file-renames.tsx
index bbe8cd23..eb882d91 100644
--- a/source/features/follow-file-renames.tsx
+++ b/source/features/follow-file-renames.tsx
@@ -50,6 +50,16 @@ async function linkify(button: HTMLButtonElement, filePath: string): Promise<voi
                return;
        }

+       // If it is a rename event and there is only one commit, that commit is the rename event -
+       // there can't be any new commits (but there can be older commits - the file has to be
+       // committed before it can be renamed). If there was one more rename, then there would be
+       // two commits in the list.
+       if (select('clipboard-copy[aria-label="Copy the full SHA"]')
+             === select.last('clipboard-copy[aria-label="Copy the full SHA"]')
+           && isNewer) {
+               return;
+       }
+
        const linkifiedURL = new GitHubURL(location.href);
        linkifiedURL.assign({
                route: 'commits',