From 5ffe1fb9f036fbd81b5e1b1fa191bd7560aa9f5c Mon Sep 17 00:00:00 2001 From: Egor Tensin Date: Wed, 23 Aug 2023 10:13:59 +0200 Subject: fetch private GitHub user repositories This is in line with how it works for Bitbucket & GitLab. --- examples/cgitize.toml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'examples/cgitize.toml') diff --git a/examples/cgitize.toml b/examples/cgitize.toml index 6f3193e..059e8ec 100644 --- a/examples/cgitize.toml +++ b/examples/cgitize.toml @@ -22,6 +22,9 @@ owner = "Your Name" # request rate limit), use "access tokens". Set in the config or using the # CGITIZE_GITHUB_TOKEN environment variable. #token = "XXX" +# Set the username that owns the token here or using the environment variable +# CGITIZE_GITHUB_USERNAME. +#username = "your-username" [github.users.me] name = "cgitize-test" @@ -55,9 +58,7 @@ dir = "python" # Access tokens are called "app passwords" on Bitbucket. # The environment variable is CGITIZE_BITBUCKET_TOKEN. #token = "XXX" -# Contrary to GitHub, Bitbucket doesn't associate app passwords with a -# username, so you also need that (CGITIZE_BITBUCKET_USERNAME is the -# environment variable). +# The environment variable is CGITIZE_BITBUCKET_USERNAME. #username = "your-username" [bitbucket.users.me] @@ -80,9 +81,7 @@ id = "berkeleylab/upc-runtime" [gitlab] # The environment variable is CGITIZE_GITLAB_TOKEN. #token = "XXX" -# Similar to Bitbucket, GitLab doesn't associate access tokens with a username -# (for HTTP clones), so you also need that (CGITIZE_GITLAB_USERNAME is the -# environment variable). +# The environment variable is CGITIZE_GITLAB_USERNAME. #username = "your-username" [gitlab.users.me] -- cgit v1.2.3