我正在尝试使用个人访问令牌与GitHub进行身份验证。在GitHub的帮助文件中，它声明使用cURL方法进行身份验证(创建个人访问令牌)。我已经尝试过了，但是我仍然无法推送到GitHub。请注意，我正试图从未经验证的服务器(特拉维斯CI)推送。
cd $HOME
git config --global user.email "emailaddress@yahoo.com"
git config --global user.name "username"
curl -u "username:<MYTOKEN>" https://github.com/username/ol3-1.git
git clone --branch=gh-pages https://github.com/username/ol3-1.git gh-pages
cd gh-pages
mkdir buildtest
cd buildtest
touch asdf.asdf
git add -f .
git commit -m "Travis build $TRAVIS_BUILD_NUMBER pushed to gh-pages"
git push -fq origin gh-pages
这段代码会导致以下错误:
remote:匿名访问scuzzlebuzz /ol3-1。git否认。
致命:'https://github.com/scuzzlebuzzle/ol3-1.git/'认证失败"
通过在应用GitHub令牌上挣扎了这么多小时，最终它的工作原理如下:
$ cf_export GITHUB_TOKEN=$(codefresh get context github——decryph -o .
Yaml | yq -y .spec.data.auth.password)
代码遵循Codefresh关于使用令牌克隆回购的指导(freestyle}
测试进行:sed %d%H%M匹配词'-123456-whatever'
推回回购(私人回购)
由DockerHub webhooks触发
以下是完整的代码:
version: '1.0'
steps:
get_git_token:
title: Reading Github token
image: codefresh/cli
commands:
- cf_export GITHUB_TOKEN=$(codefresh get context github --decrypt -o yaml | yq -y .spec.data.auth.password)
main_clone:
title: Updating the repo
image: alpine/git:latest
commands:
- git clone https://chetabahana:$GITHUB_TOKEN@github.com/chetabahana/compose.git
- cd compose && git remote rm origin
- git config --global user.name "chetabahana"
- git config --global user.email "chetabahana@gmail.com"
- git remote add origin https://chetabahana:$GITHUB_TOKEN@github.com/chetabahana/compose.git
- sed -i "s/-[0-9]\{1,\}-\([a-zA-Z0-9_]*\)'/-`date +%d%H%M`-whatever'/g" cloudbuild.yaml
- git status && git add . && git commit -m "fresh commit" && git push -u origin master
输出……
On branch master
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: cloudbuild.yaml
no changes added to commit (use "git add" and/or "git commit -a")
[master dbab20f] fresh commit
1 file changed, 1 insertion(+), 1 deletion(-)
Enumerating objects: 5, done.
Counting objects: 20% (1/5) ... Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 33% (1/3) ... Writing objects: 100% (3/3), 283 bytes | 283.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 0% (0/2) ... (2/2), completed with 2 local objects.
To https://github.com/chetabahana/compose.git
bbb6d2f..dbab20f master -> master
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reading environment variable exporting file contents.
Successfully ran freestyle step: Cloning the repo
您的curl命令完全错误。你应该使用下面的方法
curl -H 'Authorization: token <MYTOKEN>' ...
除此之外，这并没有授权您的计算机克隆存储库，如果它实际上是私有的。(然而，看一看，事实并非如此。)你通常会做的是:
git clone https://scuzzlebuzzle:<MYTOKEN>@github.com/scuzzlebuzzle/ol3-1.git --branch=gh-pages gh-pages
这将把您的凭据添加到克隆存储库时创建的远程。然而，不幸的是，您无法控制Travis如何克隆您的存储库，因此您必须像这样编辑远程。
# After cloning
cd gh-pages
git remote set-url origin https://scuzzlebuzzle:<MYTOKEN>@github.com/scuzzlebuzzle/ol3-1.git
这将使您的项目能够使用内置凭据的远程设备。
警告:令牌具有读/写访问权限，应该像密码一样对待。如果您在克隆或添加远程时将令牌输入到克隆URL中，Git会以纯文本的形式将其写入您的. Git /config文件，这就存在安全风险。
