tag:help.appveyor.com,2012-11-13:/discussions/problems/3644-pull-request-status-on-github-shows-three-appveyor-status-first-one-stays-on-yellow-foreverAppVeyor: Discussion 2018-10-19T08:17:36Ztag:help.appveyor.com,2012-11-13:Comment/385165102015-11-20T17:37:16Z2015-11-20T17:37:17ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><p>I just saw that <a href="http://help.appveyor.com/discussions/problems/3612-github-showing-multiple-checks">
http://help.appveyor.com/discussions/problems/3612-github-showing-m...</a>
seems to be about the same problem. Our case is slightly different,
though, we do have "branch protection" for the master branch but we
did not activate the "Require status checks to pass before merging"
option.</p></div>Marcel Stimbergtag:help.appveyor.com,2012-11-13:Comment/385165102015-11-20T17:55:17Z2015-11-20T17:55:17ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><p>Well, it's not quite like that. There was only one
<code>continuous-integration/appveyor</code> status before and two
separate statuses were introduced instead:
<code>continuous-integration/appveyor/branch</code> and
<code>continuous-integration/appveyor/pr</code>. Edit protected
branch settings to check
<code>continuous-integration/appveyor/pr</code> only.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/385165102015-11-20T19:02:05Z2015-11-20T19:02:05ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><p>Thanks for the quick reply. I did indeed mix up things, I guess
I was thinking about travis which had two separate statuses before.
Either way, unfortunately I cannot apply your advice since while we
protect the master branch, we do not have the "Require status
checks to pass before merging" enabled (see screenshot).</p></div>Marcel Stimbergtag:help.appveyor.com,2012-11-13:Comment/385165102015-11-20T19:05:40Z2015-11-20T19:05:40ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><p>Oh, seems like new statuses were introduced in the middle of the
build?</p>
<p>If you can tell what commit it was then you can use GitHub API
to remote that status from the commit. Or maybe it's better go
through all PR commits in a loop and check their statuses.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/385165102015-11-26T17:12:42Z2015-11-26T17:12:42ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><blockquote>
<p>Oh, seems like new statuses were introduced in the middle of the
build?</p>
</blockquote>
<p>That doesn't seem to be the reason, we are getting it for each
new pull request, e.g. this one opened two days ago: <a href="https://github.com/brian-team/brian2/pull/600">https://github.com/brian-team/brian2/pull/600</a></p>
<p>If it is the only solution for now, enabling "require status
checks to pass before merging" wouldn't be a big deal,
though...</p></div>Marcel Stimbergtag:help.appveyor.com,2012-11-13:Comment/385165102015-11-26T17:29:07Z2015-11-26T17:29:07ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><p>Yes, you should update protected branches - give it a try.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/385165102015-11-26T17:41:12Z2015-11-26T17:41:12ZPull request status on Github shows three appveyor status, first one stays on "yellow" forever<div><p>Ok, I did it -- all is looking good now. Thanks again for your
help!</p></div>Marcel Stimberg