You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tend to use the GitHub interface to propose items in the light reading section.
The README has a multi-step Linux approach to viewing the drafts. Is there a way of directly viewing a draft proposed / saved changes during the edit (I'm mainly on Git-for-Windows)? e.g. some special version of the edit's link address
The current `About Rev News` link results in a 404.
Link direct to the git.github.io page.
Fixes one point in git#545
Signed-off-by: Philip Oakley [email protected]
Sorry for the slow answer. Honestly I don't know much about Jekyll and how it works even on Linux, and I hardly ever use it.
So I think it's OK if you (or anyone else actually) send PRs that haven't been tried with Jekyll. We will figure out something if there are discrepancies between what is expected and what's actually displayed on the site. Maybe we should say that in the README.
Thanks for your PR to update the link and for your interest in improving the site!
I tend to use the GitHub interface to propose items in the light reading section.
The README has a multi-step Linux approach to viewing the drafts. Is there a way of directly viewing a draft proposed / saved changes during the edit (I'm mainly on Git-for-Windows)? e.g. some special version of the edit's link address
Also, could the README include details of how to get to the released rev_news editions, i.e. getting from /_posts/2022-01-31-edition-83.markdown to https://git.github.io/rev_news/2022/01/31/edition-83/ ?
I could suggest some words along the lines of look to the
_posts
directory and then re-arrange the markdown filename to match the release..Meanwhile the https://github.com/git/git.github.io/blob/master/rev_news/archive.md file has a bad link (404) to the "About" - which should it be - e.g. the top level README or https://git.github.io/about/ ?
The text was updated successfully, but these errors were encountered: