3 ms·
The obvious fix is to remove the repo information, but do you grandfather in old files by redirecting to the new URL? I’d say no, which I guarantee will break
by Avi-D-coder 2y ago
The obvious fix is to remove the repo information, but do you grandfather in old files by redirecting to the new URL?
I’d say no, which I guarantee will break some legitimate packages that depend on files uploaded in GitHub comments.
- pavel_lishin 2y ago> some legitimate packages that depend on files uploaded in GitHub comments I love these one-sentence horror stories.
- TheCleric 2y agoDepends might be a strong word but this would affect things like screenshots submitted in bug reports as well, which would be less than ideal at the very least.
- kevincox 2y agoThey could probably even just parse all comments and rewrite them. Then remove the redirects. If this feature is being used as intended these files should all be just linked to from comments and they parse the markdown anyways. While they are at it maybe they can expire some old files that aren't referenced...
- aprilnya 2y agoOne case I’ve seen often is the author of a repo making an issue with just some images in it, then using those image links in the README