Refined-github: Make 404 pages more useful

[fregante]

Examples:

• non-existent branch https://github.com/sindresorhus/refined-github/tree/404-branch
• existent file https://github.com/sindresorhus/refined-github/blob/shorten-url-labels/test/404.js
• deleted file https://github.com/sindresorhus/refined-github/blob/master/extension/content.js

Possible content:

• link to repo root
• link to closest existing directory
• link to last commit that had the file (example) (possible? edit: yes)

Perhaps this could be a separate extension though.

[fregante]

It could display the full URL clickable piece by piece. This URL:

https://github.com/sindresorhus/refined-github/blob/shorten-url-labels/test/404.js

would become:

sindresorhus / refined-github / shorten-url-labels / test / 404.js

It could also do a series of light HEAD fetches to the links from right to left, to gradually strikethrough each 404 link until it finds a 200 or 300.

[sindresorhus]

@bfred-it I like it!

[hkdobrev]

This is not that hard and the same time it's too good for a separate extension! 🙌

[hkdobrev]

@bfred-it The URL to the upper directory should be using tree instead of blob to save some redirects on GitHub side.

[fregante]

@hkdobrev gotcha. Yep it'd need some URL detection as well to skip the blob in the original URL and to redirect the branch part to tree/branch instead of the original URL's blob/branch.

[fregante]

• link to last commit that had the file (example) (possible?)

Idea! This file went missing:

https://github.com/sindresorhus/refined-github/blob/master/extension/content.js

Now replace blob with commits and:

https://github.com/sindresorhus/refined-github/commits/master/extension/content.js

Yep, we can get the URL to the last know commit this way. Or just link to the above.

[sindresorhus]

Cool idea. Let's do it.

[dertieran]

I started working on this https://github.com/DerTieran/refined-github/tree/useful-404-page.

Right now it is just the separat pathname parts similar to above, but for now without replacing blob with tree.

I will try to find some time to finish it or bring it to a PR ready state, but input is always welcome.

[drepram]

How did this PR started at 2017 and hasn't yet be merged

[yakov116]

@caxvis what?

[drepram]

This PR was created on 14th June 2018 and was merged to the master branch on 4th October 2018.

lololol

[fregante]

Ini tidak PR, mas

[drepram]

oh right