diff options
Diffstat (limited to '')
| -rw-r--r-- | docs/api.md | 10 | ||||
| -rw-r--r-- | docs/auth.md | 8 |
2 files changed, 9 insertions, 9 deletions
diff --git a/docs/api.md b/docs/api.md index ebf4520..f2ff319 100644 --- a/docs/api.md +++ b/docs/api.md @@ -4,10 +4,9 @@ unfortunately, peculiar in their own way. Tokens ------ -All of the forges support access tokens, of course (although they're called -"app passwords" on Bitbucket). They can be used to do `git clone https://` -with authentication info in the URL. For GitHub, it's enough to just specify -the token: +All of the forges support access tokens, of course. They can be used to do +`git clone https://` with authentication info in the URL. For GitHub, it's +enough to just specify the token: git clone https://TOKEN@github.com/USER/REPO.git @@ -16,6 +15,9 @@ token in the URL: git clone https://USER:TOKEN@bitbucket.org/USER/REPO.git +(For Bitbucket, since they deprecated their "app passwords", you need to +specify not the username, but rather the Atlassian account email.) + Terminology ----------- diff --git a/docs/auth.md b/docs/auth.md index 4eabcd5..e6ecccc 100644 --- a/docs/auth.md +++ b/docs/auth.md @@ -22,11 +22,9 @@ When using HTTPS, there're multiple options to access the private repositories. 2. Use OAuth. I thought this was too complicated to implement quickly. -3. Use per-application passwords. This option is pretty cool. Both GitHub (in - the form of "personal access tokens") and Bitbucket (calls them "app - passwords") support creating one-purpose passwords that are supposed to be - used by a single app only. They allow to bypass the 2FA also. Let's do - this! +3. Use application access tokens. This option is pretty cool. Both GitHub + and Bitbucket support creating read-only tokens. They allow to bypass the + 2FA also. Let's do this! Passing the access tokens to Git is tricky though. First, simply including them in the clone URL would be incredibly stupid, since that URL is going to be |