From 111fd0b2d9d7f5c690d343cd781d438b36806200 Mon Sep 17 00:00:00 2001 From: Joseph Nix Date: Thu, 5 Jul 2018 12:32:16 -0500 Subject: [PATCH] [gh-pages-pat] Adding note explaining the need for a personal access token and giving a link to GH's docs. --- content/docs/deployment/ghpages/contents.lr | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/deployment/ghpages/contents.lr b/content/docs/deployment/ghpages/contents.lr index 6c56e769..672362ae 100644 --- a/content/docs/deployment/ghpages/contents.lr +++ b/content/docs/deployment/ghpages/contents.lr @@ -34,6 +34,8 @@ rules apply as for the [rsync deployment method :ref](../rsync/). The HTTPS transport on the other hand accepts `--username` and `--password` which override the values in the URL. +! If you have 2-factor authentication set up and you're using HTTPS, instead of your normal password, you will need to use a [personal access token :ext](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). + ## Behavior The way this deployment support works is that it commits a new commit into a