Relink Markdown URLs

CONTRIBUTING.md

@@ -8,7 +8,7 @@ We welcome people contributing in many ways:
 
  * Donate money by using PayPal: [email protected]
 
- * Spread the word about us: http:https://gitalias.com
+ * Spread the word about us: <http:https://gitalias.com>
 
 
 ## Advice
@@ -87,7 +87,7 @@ We aim for this kind of git commit message:
  * Wrap the body at 72 characters.
  * Use the body to explain what and why vs. how.
  * For commits with more than one author, add "By: Alice <[email protected]>".
- * For commits that refer to a URL, add "See: https://example.com".
+ * For commits that refer to a URL, add "See: <https://example.com>".
  * For commits that refer to a tracker, use the complete URL, not just a number or code.
  * For more information:
  * [Git commit message](https://github.com/joelparkerhenderson/git-commit-message/)

doc/contribute/index.md

@@ -8,7 +8,7 @@ We welcome people contributing in many ways:
 
  * Donate money by using PayPal: [email protected]
 
- * Spread the word about us: https://gitalias.com
+ * Spread the word about us: <https://gitalias.com>
 
 
 ## Conventions
@@ -94,7 +94,7 @@ Body:
 
  * For commits with more than one author, add "By: Alice <[email protected]>".
 
- * For commits that refer to a URL, add "See: https://example.com".
+ * For commits that refer to a URL, add "See: <https://example.com>".
 
  * For commits that refer to a tracker, use the complete URL, not just a number or code.
 

doc/git-aliases/index.md

@@ -26,4 +26,4 @@ Our friendly wording for plurals:
 
 * [git tags](../git-tags)
 
-Thanks to http:https://gggritso.com/human-git-aliases
+Thanks <http:https://gggritso.com/human-git-aliases>

doc/git-assume-and-git-unassume/index.md

@@ -45,6 +45,6 @@ modified passwords.txt
 modified foo.txt
 ```
 
-Thanks to http:https://durdn.com/blog/2012/11/22/must-have-git-aliases-advanced-examples/
+Thanks <http:https://durdn.com/blog/2012/11/22/must-have-git-aliases-advanced-examples/>
 
-Thanks to http:https://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/
+Thanks <http:https://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/>

doc/git-branch-commit/index.md

@@ -11,4 +11,4 @@ Inspirations:
 
  * Email from Demian proposing these aliases
 
- * https://github.com/hutusi/git-paging
+ * <https://github.com/hutusi/git-paging>

doc/git-branches/index.md

@@ -20,4 +20,4 @@ Our friendly wording for plurals:
 
 * [git tags](../git-tags)
 
-Thanks to http:https://gggritso.com/human-git-aliases
+Thanks <http:https://gggritso.com/human-git-aliases>

doc/git-churn/index.md

@@ -73,8 +73,8 @@ Credit:
 
 * Scriptified by Gary Bernhardt
 
-* Obtained from https://github.com/garybernhardt/dotfiles/blob/main/bin/git-churn
+* Obtained from <https://github.com/garybernhardt/dotfiles/blob/main/bin/git-churn>
 
-* Comments by Mislav http:https://mislav.uniqpath.com/2014/02/hidden-documentation/
+* Comments by Mislav <http:https://mislav.uniqpath.com/2014/02/hidden-documentation/>
 
 * Edited for GitAlias.com repo by Joel Parker Henderson

doc/git-clone-lean/index.md

@@ -42,4 +42,4 @@ An extension was made to the Git remote protocol to support this
 feature in v2.19.0 and actually skip fetching unneeded objects.
 There was server support then, but it can be locally tested.
 
-Credit: https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/52269934#52269934
+Credit <https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/52269934#52269934>

doc/git-expunge/index.md

@@ -26,4 +26,4 @@ confidential information.
 
 After you use this command, you will likely need to force push everything.
 
-See https://help.github.com/articles/removing-sensitive-data-from-a-repository/
+See <https://help.github.com/articles/removing-sensitive-data-from-a-repository/>

doc/git-fixup/index.md

@@ -17,6 +17,6 @@ Example:
 git fixup
 ```
 
-See https://blog.filippo.io/git-fixup-amending-an-older-commit/
+See <https://blog.filippo.io/git-fixup-amending-an-older-commit/>
 
 This alias is a slightly modified version.

doc/git-heads/index.md

@@ -14,4 +14,4 @@ Example:
 git heads
 ```
 
-From https://gist.github.com/492227
+Thanks <https://gist.github.com/492227>

doc/git-prp/index.md

@@ -14,7 +14,7 @@ Example:
 git prp
 ```
 
-See https://stackoverflow.com/questions/21364636/git-pull-rebase-preserve-merges
+See <https://stackoverflow.com/questions/21364636/git-pull-rebase-preserve-merges>
 
 You should only rebase if you know (in a sort of general sense)
 what you are doing, and if you do know what you are doing, then you
@@ -29,7 +29,7 @@ That is, if it's appropriate to do a rebase at all, it's at least fairly
 likely that the history to be rebased is itself linear, so that the
 preserve-vs-flatten question is moot anyway.
 
-See https://stackoverflow.com/questions/38269092/is-it-possible-to-put-preserve-merges-in-the-gitconfig
+See <https://stackoverflow.com/questions/38269092/is-it-possible-to-put-preserve-merges-in-the-gitconfig>
 
 While preserving merges is probably generally superior, in at least a
 few ways, to discarding them when rebasing, the fact is that rebase

doc/git-snapshot/index.md

@@ -33,4 +33,4 @@ stash@{0}: On feature/handy-git-tricks: snapshot: Mon Apr 8 12:39:06 BST 2013
 
 … and seemingly no changes to your working tree.
 
-From http:https://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/
+From <http:https://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/>

doc/git-stashes/index.md

@@ -26,4 +26,4 @@ Our friendly wording for plurals:
 
 * [git tags](../git-tags)
 
-Thanks to http:https://gggritso.com/human-git-aliases
+Thanks <http:https://gggritso.com/human-git-aliases>

doc/git-tags/index.md

@@ -26,4 +26,4 @@ Our friendly wording for plurals:
 
 * [git tags](../git-tags)
 
-Thanks to http:https://gggritso.com/human-git-aliases
+Thanks <http:https://gggritso.com/human-git-aliases>

doc/git-wip-git-unwip/index.md

@@ -26,5 +26,5 @@ due to an "unclean" working directory (not in sync with the index).
 
 The unwip alias is a quick way to restore deleted files to the working tree.
 
-From https://gist.github.com/492227 and VonC on stackoverflow.
+From <https://gist.github.com/492227> and VonC on stackoverflow.
 

gitalias.txt

@@ -302,7 +302,7 @@
 
  # prp - Pull with rebase preserve of merge commits
  #
- # See https://stackoverflow.com/questions/21364636/git-pull-rebase-preserve-merges
+ # See <https://stackoverflow.com/questions/21364636/git-pull-rebase-preserve-merges>
  #
  # You should only rebase if you know (in a sort of general sense)
  # what you are doing, and if you do know what you are doing, then you
@@ -317,7 +317,7 @@
  # likely that the history to be rebased is itself linear, so that the
  # preserve-vs-flatten question is moot anyway.
  #
- # See https://stackoverflow.com/questions/38269092/is-it-possible-to-put-preserve-merges-in-the-gitconfig
+ # See <https://stackoverflow.com/questions/38269092/is-it-possible-to-put-preserve-merges-in-the-gitconfig>
  #
  # While preserving merges is probably generally superior, in at least a
  # few ways, to discarding them when rebasing, the fact is that rebase
@@ -390,7 +390,7 @@
  #
  rbiu = rebase --interactive @{upstream}
 
- # See https://blog.filippo.io/git-fixup-amending-an-older-commit/
+ # See <https://blog.filippo.io/git-fixup-amending-an-older-commit/>
  # This is a slightly modified version
  fixup = "!f() { TARGET=$(git rev-parse \"$1\"); git commit --fixup=$TARGET && GIT_EDITOR=true git rebase --interactive --autosquash $TARGET~; }; f"
 
@@ -510,7 +510,7 @@
  # Last annotated tag in all branches
  last-tagged = !git describe --tags `git rev-list --tags --max-count=1`
 
- # From https://gist.github.com/492227
+ # From <https://gist.github.com/492227>
  heads = !"git log origin/main.. --format='%Cred%h%Creset;%C(yellow)%an%Creset;%H;%Cblue%f%Creset' | git name-rev --stdin --always --name-only | column -t -s';'"
 
  ### diff-* aliases ###
@@ -749,9 +749,9 @@
  #
  # * Written by [Corey Haines](http:https://coreyhaines.com/)
  # * Scriptified by Gary Bernhardt
- # * Obtained from https://github.com/garybernhardt/dotfiles/blob/main/bin/git-churn
+ # * Obtained from <https://github.com/garybernhardt/dotfiles/blob/main/bin/git-churn>
  # * Edited for GitAlias.com repo by Joel Parker Henderson
- # * Comments by Mislav http:https://mislav.uniqpath.com/2014/02/hidden-documentation/
+ # * Comments by Mislav <http:https://mislav.uniqpath.com/2014/02/hidden-documentation/>
  #
  # Show churn for whole repo:
  #
@@ -1196,7 +1196,7 @@
  # Expunge a file everywhere; this command is typically for a serious problem,
  # such as accidentally committing a file of sensitive data, such as passwords.
  # After you use command, you will likely need to force push everything.
- # See https://help.github.com/articles/removing-sensitive-data-from-a-repository/
+ # See <https://help.github.com/articles/removing-sensitive-data-from-a-repository/>
  expunge = !"f() { git filter-branch --force --index-filter \"git rm --cached --ignore-unmatch $1\" --prune-empty --tag-name-filter cat -- --all }; f"
 
  # Show logs of unreachable commits.
@@ -1248,7 +1248,7 @@
 
  # Work In Progress - Easy tracking of what you're doing
  #
- # From https://gist.github.com/492227 and VonC on stackoverflow.
+ # From <https://gist.github.com/492227> and VonC on stackoverflow.
  #
  # This enables a quick way to add all new and modified files to the index,
  # while cleaning the index from the files removed from the working tree;
@@ -1290,8 +1290,8 @@
  # modified passwords.txt
  # modified foo.txt
  #
- # Thanks to http:https://durdn.com/blog/2012/11/22/must-have-git-aliases-advanced-examples/
- # Thanks to http:https://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/
+ # Thanks <http:https://durdn.com/blog/2012/11/22/must-have-git-aliases-advanced-examples/>
+ # Thanks <http:https://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/>
  #
  assume = update-index --assume-unchanged
  unassume = update-index --no-assume-unchanged