What is the exact GitHub permission level required to enable Travis CI for a repo owned by an organization?

The tutorial states that owner permissions are required, but I get the sense it’s not the full story…

My guess is:

GitHub App based integration

  • User needs to be a GitHub App manger in the organization. This can be:

Legacy Webhook integration

  • User needs to be able to change repository settings of the repo being enabled. This can be:
    • Organization owners
    • Repository admins

Does this sound right?

Motivation for asking: I’m looking into reorganizing permission levels granted to various teams in the organization, and am wondering if it’s possible to grant the engineering team the necessary permission to enable Travis CI on their own.

2 Likes

I really would like to know the answer to this as well… It seems I’m an organization owner (didn’t realize until I checked) but I still can’t see the repo in the list on https://travis-ci.com/

Edit: I found it. On Travis CI - Test and Deploy with Confidence there’s this note:

MISSING AN ORGANIZATION?

Review and add your authorized organizations.

And that worked for me.

1 Like