Any alternate method to view the latest drafts or PRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git, github, markdown
- Domain
- documentation
Research direction
Read the README's existing Linux draft-viewing instructions, then inspect _posts/2022-01-31-edition-83.markdown and rev_news/archive.md. Document how to reach released editions from _posts and clarify the available draft or saved-change workflow; correct the broken About link and verify the referenced URLs resolve.
Written by the indexing model from the issue text.
Description
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/ ?
- Dominant language
- CSS
- Stars
- 373
- Forks
- 325
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from git/git.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
git/git.github.io#860 · 7 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
git/git.github.io#864 · 5 comments ·
-
Automatically intimate regarding [ANNOUNCE] mails in the current month edition's issue comments? Open
git/git.github.io#863 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
git/git.github.io#862 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
git/git.github.io#830 · 4 comments ·
All issues in git/git.github.io
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100