Home → Knowledge Base →

Show multiple statuses in GitHub Pull Requests

• Edit

Feodor Fitsner

Aug 22, 2014 @ 09:57 PM

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.

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:

http://github-multi-status.herokuapp.com/

PLEASE NOTE: This is a third-party application supported by its creators.

1. 1 Posted by chrisdembia on Dec 08, 2014 @ 08:31 PM

   

   GitHub now supports this without the need for addons: https://github.com/blog/1935-see-results-from-all-pull-request-status-checks

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on Dec 08, 2014 @ 08:36 PM

   

   Wow, this is great news!

   -Feodor

   • Edit

3. 3 Posted by gep13 on Jan 20, 2015 @ 07:34 AM

   

   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?

   Thanks!

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on Jan 20, 2015 @ 03:33 PM

   

   Sure, we do specify context.

   -Feodor

   • Edit

5. 5 Posted by gep13 on Jan 20, 2015 @ 07:39 PM

   

   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 :-)

   • Edit

6. 6 Posted by Eilon [Microsof... on May 12, 2015 @ 06:00 AM

   

   Hi there,

   We recently added a repo called Localization to our org at https://github.com/aspnet/Localization/ . 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.

   Is there anything special I need to do to enable the CI status to show up in the PR?

   Thanks,
   Eilon

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on May 12, 2015 @ 04:38 PM

   

   Hi Eilon,

   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: https://ci.appveyor.com/account

   Please let me know if you have any questions.

   • Edit

8. 8 Posted by Eilon Lipton on May 13, 2015 @ 10:22 PM

   

   Hi Feodor,

   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.

   Thanks,
   Eilon

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on May 13, 2015 @ 10:29 PM

   

   Great, thanks for the update!

   • Edit

10. 10 Posted by thomas.levesque on Sep 29, 2016 @ 12:24 PM

    

    Hi,

    Currently it seems Appveyor always sends continuous-integration/appveyor/pr 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.

    Thanks

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on Sep 30, 2016 @ 04:36 PM

    

    Hi Thomas,

    So, you have 2 projects for the same repository? Could you please clarify?

    • Edit

12. 12 Posted by thomas.levesque on Sep 30, 2016 @ 04:40 PM

    

    Hi Feodor,

    Yes, exactly (I meant "same project" not "same projects"). 2 AppVeyor projects for a single GitHub repo.

    • Edit

13. Support Staff 13 Posted by Feodor Fitsner on Sep 30, 2016 @ 10:48 PM

    

    Yes, there is a limitation right now. Both projects will be using the same status context and "compete" with each other.

    I've added a new issue: https://github.com/appveyor/ci/issues/1083

    • Edit

14. 14 Posted by thomas.levesque on Sep 30, 2016 @ 11:36 PM

    

    Thanks Feodor!

    • Edit

15. Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:09 AM.