increase importance of pats by including it as a section in the tutorials

Signed-off-by: Kenji Brameld <[email protected]>

Author: ijnek

source/How-To-Guides/Releasing/First-Time-Release.rst

@@ -28,6 +28,11 @@ Install dependencies
 
 .. include:: _Install-Dependencies.rst
 
+Set Up a Personal Access Token
+------------------------------
+
+.. include:: _Personal-Access-Token.rst
+
 Ensure repositories are up-to-date
 ----------------------------------
 
@@ -52,10 +57,6 @@ Bump the package version
 Bloom Release
 -------------
 
-.. note::
-
-   If you have two factor authorization enabled on GitHub, follow :doc:`GitHub Manual Authorization <GitHub-Manual-Authorization>` first.
-
 Run the following command, replacing ``my_repo`` with the name of your repository:
 
 .. code-block:: bash

source/How-To-Guides/Releasing/GitHub-Manual-Authorization.rst

@@ -15,10 +15,9 @@ Releasing a Package
    Subsequent-Releases
    Release-Team-Repository
    Release-Track
-   GitHub-Manual-Authorization
 
 **Releasing a package makes your package available on the public ROS 2 buildfarm.**
-After you've created a package, this is the next step towards getting your package into the publicly available Debian packages!
+After you have created a package, this is the next step towards getting your package into the publicly available Debian packages!
 
 Releasing your package onto the buildfarm will make your package available to be installed via package managers (eg. ``apt`` on Ubuntu) for all supported Linux platforms in a ROS distribution as described in `REP 2000 <https://ros.org/reps/rep-2000.html>`_.
 

source/How-To-Guides/Releasing/Releasing-a-Package.rst

@@ -17,6 +17,11 @@ Install dependencies
 
 .. include:: _Install-Dependencies.rst
 
+Set up a Personal Access Token
+------------------------------
+
+.. include:: _Personal-Access-Token.rst
+
 Ensure repositories are up-to-date
 ----------------------------------
 
@@ -41,10 +46,6 @@ Bump the package version
 Bloom Release
 -------------
 
-.. note::
-
-   If you have two factor authorization enabled on GitHub, follow :doc:`GitHub Manual Authorization <GitHub-Manual-Authorization>` first.
-
 Run the following command, replacing ``my_repo`` with the name of your repository with the packages:
 
 .. code-block:: bash

source/How-To-Guides/Releasing/Subsequent-Releases.rst

@@ -0,0 +1,27 @@
+.. warning::
+
+   If the file ``~/.config/bloom`` exists on your computer, it is likely that you have done this before so you should skip this section.
+
+During the release process, multiple HTTPS Git operations will be performed that require password authentication.
+To avoid being repeatedly asked for a password, a `Personal Access Token (PAT) <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token>`_ will be set up.
+
+Create a Personal Access Token by:
+
+#. Log in to GitHub and go to `Personal access tokens <https://github.com/settings/tokens>`_.
+#. Click the **Generate new token** button.
+#. Set **Note** to something like ``Bloom token``.
+#. Set **Expiration** to **No expiration**.
+#. Tick the ``public_repo`` and ``workflow`` checkboxes.
+#. Click the **Generate token** button.
+
+After you have created the token, you will end up back at the *Personal access tokens* page.
+**Copy the alphanumeric token** that is highlighted in green.
+
+Save your GitHub username and PAT to a new file called ``~/.config/bloom``, with the format below:
+
+.. code-block:: text
+
+   {
+      "github_user": "<your-github-username>",
+      "oauth_token": "<token-you-created-for-bloom>"
+   }