无法突然推动github [英] Cannot push on github suddently

查看:106
本文介绍了无法突然推动github的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

嗯,这很奇怪.我正在使用Github保护规则来强制执行拉取请求并为每次推送触发TravisCI.但是,由于进行连续翻译,因此我需要一个能够在不发出请求请求的情况下进行推送并且避免TravisCI状态检查的用户(为此,我使用[ci skip]).该用户包括在Github在分支保护规则中提供的白名单中.自上周以来,它运行良好,突然间,当我尝试与该用户推送时,我收到了它:

Well, it is very weird. I'm using Github protection rules to enforce to make pull requests and to trigger TravisCI for every push. However, because of continuous translation, I need a user who should be able to push without making a pull request and avoiding TravisCI status check (for that I use [ci skip]). This user is included in the white list that Github provides in branch protection rules. It worked perfect since last week, suddently when I try to push with this user I receive it:

remote: Resolving deltas: 100% (5/5), completed with 5 local objects. remote: error: GH006: Protected branch update failed for refs/heads/master. remote: error: Required status check "Travis CI - Pull Request" is expected. At least 1 approving review is required by reviewers with write access. To https://github.com/***** ! [remote rejected] master -> master (protected branch hook declined) error: failed to push some refs to 'https://*****'

remote: Resolving deltas: 100% (5/5), completed with 5 local objects. remote: error: GH006: Protected branch update failed for refs/heads/master. remote: error: Required status check "Travis CI - Pull Request" is expected. At least 1 approving review is required by reviewers with write access. To https://github.com/***** ! [remote rejected] master -> master (protected branch hook declined) error: failed to push some refs to 'https://*****'

这很奇怪,因为它一直可以使用到现在...而且用户有权进行推送而不发出请求,并且它通过提交消息跳过了Travis,所以我不明白为什么github询问我有关状态的信息检查和批准...

It is very weird since it worked always til now... And the user has permissions to push without making a pull request and it is skipping Travis with through the commit message so I do not understand why github is asking me about status check and approvals...

推荐答案

我解决了它,最终为用户提供了管理员访问权限,而不仅仅是写访问权限.现在,它可以避免批准和状态检查.但是我不明白为什么为什么只在保护分支规则的白名单中行不通呢...以前行得通,好像GitHub做了一些更改...

I solved it finally giving admin access to the user instead of just write access. Now it is able to push avoiding approvals and status check. But I don't understand why does not work just being in the white list of protection branch rules... It worked before, looks like GitHub made some changes...

这篇关于无法突然推动github的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆