From e0decc051f0d8e97016673d96f41f919831f89ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alain=20H=C3=A9la=C3=AFli?= Date: Thu, 16 May 2024 17:28:58 +0200 Subject: [PATCH] Moar doc --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 458e6a2..35df60d 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ Automate the approval of fine grained Personal Access Tokens in GitHub. You can now define a maximum duration for fine grained PAT and automatically approve or reject them. -[!NOTE] Organization admins can still create long lived PATs. +> [!NOTE] +> Organization admins can still create long lived PATs. # Usage @@ -28,7 +29,8 @@ Users now need to create a fine grained PAT with a short enough duration. When a Cloning repos using `git clone https://github_pat_xxxxxx@github.com//`. -[!WARNING] Users still can use SSH keys to clone repos without the need for a PAT. If you want to enforce the use of PATs, you need to force the use of HTTPS URLs in your organization. Currently, the only way to do this is: +> [!WARNING] +> Users still can use SSH keys to clone repos without the need for a PAT. If you want to enforce the use of PATs, you need to force the use of HTTPS URLs in your organization. Currently, the only way to do this is: - use a VPN and block the SSH port - configure IP allow lists in your organization to force the use of the VPN