Skip to content
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

Any alternate method to view the latest drafts or PRs #545

Open
PhilipOakley opened this issue Jan 31, 2022 · 1 comment
Open

Any alternate method to view the latest drafts or PRs #545

PhilipOakley opened this issue Jan 31, 2022 · 1 comment

Comments

@PhilipOakley
Copy link
Contributor

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/ ?

PhilipOakley added a commit to PhilipOakley/git.github.io that referenced this issue Feb 1, 2022
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]
@chriscool
Copy link
Collaborator

chriscool commented Feb 12, 2022

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants