Check the organization’s 3rd party access restrictions and approve Coveralls. More info here: https://help.github.com/articles/approving-third-party-applications-for-your-organization/
Have them refresh their repos here: https://coveralls.io/refresh?private=true
Make sure you have “service_name: travis-pro” in your .coveralls.yml.
Travis uses non-unique job id’s between its free and pro services, so when Coveralls doesn’t know that your service-name is Travis-pro, it looks up the info for those job ids using the free Travis API – that’s why they will show random committers, etc. The opposite cannot happen with the proper credentials, so you don’t need to worry that your data is leaking out. Once your ENV var is set to specify travis-pro, the correct info will be pulled from Travis’s pro API.
If your membership of an organization is not publicized (your username isn’t listed on the organization’s Github page), Coveralls can’t see it either, so you’ll need to upgrade your OAuth scope to private here:
You need to have admin permissions on Github for the repo in order to access/regenerate its token on Coveralls. If you do and our data is out of sync, please re-sync your repos here: https://coveralls.io/refresh