All committers have signed the CLA.

@npentrel to close the ➿, having a look into whether this is fixable on the jekyll side (i.e. in the handling of relative links) because that would mean docs writers don't have to change how they write the docs. However I think this is probably due to the use of this gem and it assuming that all relative links are to other docs in the static site, which is why it's failing to make good links for these build files...looking into it

@npentrel Ah, ok think I've got it!

jekyll-relative-links can be set to exclude certain directories and files from it's conversion in the site's _config.yml. So the files for which you've had to change the URLs to absolute here can be added to that instead, or the directory when that directory isn't root, I think.

It seems you can only exclude whole files or whole directories. There's files that contain relative links to the repo and to the docs - so excluding the file would break the other links. 🤷‍♀️

Hmm ok. I'd like to find a solution to this that doesn't involve diving into that gem...I would prefer we do absolute paths in that case but as they're GitHub URLs, @iamrecursion's concern is that will break docs navigation in local clones.

Hi @npentrel! Thanks so much for this contribution! Has there been any luck fixing this on the Jekyll side?

This is a substantial problem on the Jekyll side. I'm going to close this for now whilst I find a way to do it, but there is a chance this could circle back round to it being easier to absolute link these things.