Update references to "Git reference" #16968
Conversation
The "Git reference" is created and maintained by GitHub, not by the Git community, so use "our" to refer to it.
The URL 'gitref.org' for the "Git Reference" does not work since August 2017 [1]. Fix the URL to point to the right place, and use an HTTPS URL. [1] git/git-reference#112
The interactive "Try Git" tutorial that used to be available at 'try.github.com' [1] is not available since 2018 [2]. Stop mentioning it. [1] https://github.blog/2012-07-04-try-git-in-your-browser/ [2] git/git-scm.com#1239
Automatically generated comment
|
| Source | Preview | Production | What Changed |
|---|---|---|---|
| content/get-started/quickstart/git-and-github-learning-resources.md | Modified | Original |
Denote Markdown files as such with the 'diff' Git attribute [1]. This
allows various Git commands (diff [2, 3], grep [4, 5], log [6], blame
[7]) to show in which part of the "code" the changes are located in the
hunk header.
The history of the "Using Git" section modified in the previous commit
specific entry can now be interrogated using
git log -L:"Using Git":content/get-started/quickstart/git-and-github-learning-resources.md
[1] https://git-scm.com/docs/gitattributes#_defining_a_custom_hunk_header
[2] https://git-scm.com/docs/git-diff#_generating_patch_text_with_p
[3] https://git-scm.com/docs/git-diff#Documentation/git-diff.txt--W
[4] https://git-scm.com/docs/git-grep#Documentation/git-grep.txt--p
[5] https://git-scm.com/docs/git-grep#Documentation/git-grep.txt--W
[6] https://git-scm.com/docs/git-log#Documentation/git-log.txt--Lltfuncnamegtltfilegt
[7] https://git-scm.com/docs/git-blame#Documentation/git-blame.txt--Lltfuncnamegt
|
@phil-blain |
@phil-blain - thank you for taking the time to track down the missing site and open this PR to fix the references. Your help is much appreciated
It looks as if one of the other references is no longer maintained, so I'm going to remove that link too. When we've resolved the question of the .gitattributes file, this pull request will be ready to merge.
| @@ -18,7 +18,7 @@ shortTitle: Learning resources | |||
| --- | |||
| ## Using Git | |||
|
|
|||
| Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator. | |||
| Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs) or our [Git command lookup reference](https://git.github.io/git-reference/). | |||
There was a problem hiding this comment.
Thank you for removing the outdated link a git simulator and for tracking down the Git command reference that's backed by https://github.com/git/git-reference.
It looks as if the Git command reference is no longer actively maintained, so I suggest we remove this reference too.
| Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs) or our [Git command lookup reference](https://git.github.io/git-reference/). | |
| Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs). |
There was a problem hiding this comment.
Well, I agree it does not look actively maintained, but it did help me at first when I was learning Git. So it's you call :)
There was a problem hiding this comment.
It's good to know you found this resource useful, even though it's not actively maintained. I guess the core functionality of Git doesn't change much.
@phil-blain - thanks for your patience with our review process
@rsese - thank you for confirming that the change to .gitattributes is safe 🙇🏻♀️
This looks ready to merge. Thanks for your help.
|
Thanks very much for contributing! Your pull request has been merged |
Why:
Update the "Using Git" section of the page "Git and GitHub learning resources" to bring it up to date.
What's being changed:
Notes from the commit messages...
git-and-github-learning-resources: mark "Git reference" as GitHub's
The "Git reference" is created and maintained by GitHub, not by the Git
community, so use "our" to refer to it.
git-and-github-learning-resources: fix URL for Git reference
The URL 'gitref.org' for the "Git Reference" does not work since August
2017 [1]. Fix the URL to point to the right place, and use an HTTPS URL.
[1] git/git-reference#112
git-and-github-learning-resources: remove "Try Git" reference
The interactive "Try Git" tutorial that used to be available at
'try.github.com' [1] is not available since 2018 [2]. Stop mentioning
it.
[1] https://github.blog/2012-07-04-try-git-in-your-browser/
[2] git/git-scm.com#1239
.gitattributes: mark '*.md' as Markdown files
Denote Markdown files as such with the 'diff' Git attribute [1]. This
allows various Git commands (diff [2, 3], grep [4, 5], log [6], blame
[7]) to show in which part of the "code" the changes are located in the
hunk header.
The history of the "Using Git" section modified in the previous commit
specific entry can now be interrogated using
git log -L:"Using Git":content/get-started/quickstart/git-and-github-learning-resources.md
[1] https://git-scm.com/docs/gitattributes#_defining_a_custom_hunk_header
[2] https://git-scm.com/docs/git-diff#_generating_patch_text_with_p
[3] https://git-scm.com/docs/git-diff#Documentation/git-diff.txt--W
[4] https://git-scm.com/docs/git-grep#Documentation/git-grep.txt--p
[5] https://git-scm.com/docs/git-grep#Documentation/git-grep.txt--W
[6] https://git-scm.com/docs/git-log#Documentation/git-log.txt--Lltfuncnamegtltfilegt
[7] https://git-scm.com/docs/git-blame#Documentation/git-blame.txt--Lltfuncnamegt
Update content/get-started/quickstart/git-and-github-learning-resources.md
Check off the following:
Writer impact (This section is for GitHub staff members only):