-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Github-Only Comments to point users to ReadTheDocs #247
Comments
They do work if access via this interface: https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/ |
Yeah, that's much better and IT IS a beauty! I don't know if it would also be straightforward to make this raw RFC interface also browsable to some extent. There will be developers who just get to the raw RFCs repo. @gonsie or @SteVwonder: any idea? As is, I can't even jump through the hyperlinks via our README files. Clicking on "in the Index" takes me to a page that I can't follow links any longer. My guess is it would probably be GitHub RST render so I don't know if there would be an easy fix: |
The internal links within the RFCs use the My suggestion would be to follow the advice at the top of GitHub's markup renderer [4]:
We could add text (and a link) to the top of every file (including the Markdown readme) that would only show when rendered on GitHub that points people to the readthedocs site. The magic string to add to the start of the comment so that it only shows on GitHub is |
The README that is rendered on the "homepage" of this repo is the |
|
@SteVwonder can you explain the |
nvm, I got it. |
I was browsing some of RFCs and it appears I can no longer follow the links using my Safari web browser. Example: trying to go to RFC12 from within RFC 16.
Is this happening after we convert our RFC to the RST format?
The text was updated successfully, but these errors were encountered: