tag:help.appveyor.com,2012-11-13:/discussions/kb/4-show-multiple-statuses-in-github-pull-requestsAppVeyor: Discussion 2018-10-19T08:16:42Ztag:help.appveyor.com,2012-11-13:Comment/342501842014-08-22T21:57:53Z2014-08-22T21:59:16ZShow multiple statuses in GitHub Pull Requests<div><p>Currently, GitHub only allows one status to be shown in the
status bar of a pull request. If using two continuous integration
services, such as Travis and AppVeyor, the last updated status is
the one shown, which means that it is not possible to see the
status from both systems at the same time.</p>
<p>This site provides a simple webapp that allows you to show
statuses from multiple continuous integration tools in the status
bar of a GitHub pull request:</p>
<p><a href=
"http://github-multi-status.herokuapp.com/">http://github-multi-status.herokuapp.com/</a></p>
<p>PLEASE NOTE: This is a third-party application supported by its
creators.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842014-12-08T20:31:24Z2014-12-08T20:31:26ZShow multiple statuses in GitHub Pull Requests<div><p>GitHub now supports this without the need for addons: <a href=
"https://github.com/blog/1935-see-results-from-all-pull-request-status-checks">
https://github.com/blog/1935-see-results-from-all-pull-request-stat...</a></p></div>chrisdembiatag:help.appveyor.com,2012-11-13:Comment/342501842014-12-08T20:36:57Z2014-12-08T20:36:57ZShow multiple statuses in GitHub Pull Requests<div><p>Wow, this is great news!</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842015-01-20T07:34:09Z2015-01-20T07:34:09ZShow multiple statuses in GitHub Pull Requests<div><p>Feodor, is this now supported by AppVeyor? Do you specify the
"context" when sending notification from AppVeyor? i.e. something
like continuousintegration/appveyor? Or is this configurable?</p>
<p>Thanks!</p></div>gep13tag:help.appveyor.com,2012-11-13:Comment/342501842015-01-20T15:33:16Z2015-01-20T15:33:16ZShow multiple statuses in GitHub Pull Requests<div><p>Sure, we do specify context.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842015-01-20T19:39:07Z2015-01-20T19:39:07ZShow multiple statuses in GitHub Pull Requests<div><p>Thanks for getting back to me. Yeah, we got it all working. We
were seeing some strangeness when trying to set up status
notifications for both AppVeyor and TeamCity, but it is all working
now :-)</p></div>gep13tag:help.appveyor.com,2012-11-13:Comment/342501842015-05-12T06:00:29Z2015-05-12T06:00:30ZShow multiple statuses in GitHub Pull Requests<div><p>Hi there,</p>
<p>We recently added a repo called Localization to our org at
<a href="https://github.com/aspnet/Localization/">https://github.com/aspnet/Localization/</a>
. I've been trying to enable AppVeyor to show the CI status in the
PR but it doesn't show up. We also have Travis enabled and that one
shows up fine. I do have AppVeyor enabled though I had to manually
create the web hook, but I can see AppVeyor running the builds and
all. It's just not showing the CI status in the PR. For all our
other repos this is working fine.</p>
<p>Is there anything special I need to do to enable the CI status
to show up in the PR?</p>
<p>Thanks,<br>
Eilon</p></div>Eilon [Microsoft]tag:help.appveyor.com,2012-11-13:Comment/342501842015-05-12T16:38:25Z2015-05-12T16:38:25ZShow multiple statuses in GitHub Pull Requests<div><p>Hi Eilon,</p>
<p>You said there was no webhook automatically added to that
repository and then you added it manually. This is the reason why
there is no status set on Pull Requests - GitHub user currently
authorized in AppVeyor doesn't have "write" (and "admin" for
placing webhook) rights on that repository. You can see (and
re-authorize) GitHub user linked to AppVeyor account on this page:
<a href="https://ci.appveyor.com/account">https://ci.appveyor.com/account</a></p>
<p>Please let me know if you have any questions.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842015-05-13T22:22:30Z2015-05-13T22:22:30ZShow multiple statuses in GitHub Pull Requests<div><p>Hi Feodor,</p>
<p>Thank you, I got it working! You are correct and the user I use
to run the AppVeyor builds didn’t have the correct
permissions on the new repo I added. I fixed the permissions and
now everything works.</p>
<p>Thanks,<br>
Eilon</p></div>Eilon Liptontag:help.appveyor.com,2012-11-13:Comment/342501842015-05-13T22:29:51Z2015-05-13T22:29:51ZShow multiple statuses in GitHub Pull Requests<div><p>Great, thanks for the update!</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842016-09-29T12:24:57Z2018-09-07T07:39:23ZShow multiple statuses in GitHub Pull Requests<div><p>Hi,</p>
<p>Currently it seems Appveyor always sends <code>continuous-integration/appveyor/pr</code> as the context. Is there a way to change it? We have two Appveyor builds for the same projects, but since they have the same context, only one of them shows up in pull-requests.</p>
<p>Thanks</p></div>thomas.levesquetag:help.appveyor.com,2012-11-13:Comment/342501842016-09-30T16:36:23Z2016-09-30T16:36:23ZShow multiple statuses in GitHub Pull Requests<div><p>Hi Thomas,</p>
<p>So, you have 2 projects for the same repository? Could you
please clarify?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842016-09-30T16:40:57Z2018-09-07T07:39:23ZShow multiple statuses in GitHub Pull Requests<div><p>Hi Feodor,</p>
<p>Yes, exactly (I meant "same project" not "same projects"). 2 AppVeyor projects for a single GitHub repo.</p></div>thomas.levesquetag:help.appveyor.com,2012-11-13:Comment/342501842016-09-30T22:48:41Z2016-09-30T22:48:41ZShow multiple statuses in GitHub Pull Requests<div><p>Yes, there is a limitation right now. Both projects will be
using the same status context and "compete" with each other.</p>
<p>I've added a new issue: <a href="https://github.com/appveyor/ci/issues/1083">https://github.com/appveyor/ci/issues/1083</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/342501842016-09-30T23:36:34Z2018-09-07T07:39:23ZShow multiple statuses in GitHub Pull Requests<div><p>Thanks Feodor!</p></div>thomas.levesque