When looking at the URLs that points to the resources of a repository, it seems that the browser interprets anything that is not an external URL into a local path.
For example, if a repo README points to a file such as [my_file](src/my_file), the path for my_file becomes http://localhost:3000/repositories/src/my_file (With localhost:3000 being our app local dev url) when the expected URL should be one pointing into the github domain.
We could prefix either https://github.com or https://raw.githubusercontent.com to the parenthesis that has the relative path. The issue with the raw content page is that it gives a Bad Request error if the pointed resource is a directory instead of a file. Because of it, I'm more inclined to use the github.com domain since that matches the original intend of the README.
When looking at the URLs that points to the resources of a repository, it seems that the browser interprets anything that is not an external URL into a local path.
For example, if a repo README points to a file such as
[my_file](src/my_file), the path formy_filebecomeshttp://localhost:3000/repositories/src/my_file(With localhost:3000 being our app local dev url) when the expected URL should be one pointing into the github domain.We could prefix either
https://github.comorhttps://raw.githubusercontent.comto the parenthesis that has the relative path. The issue with the raw content page is that it gives a Bad Request error if the pointed resource is a directory instead of a file. Because of it, I'm more inclined to use the github.com domain since that matches the original intend of the README.