# Would like to connect a repo to Travis CI, but the GitHub scope asks for a lot

**URL:** <https://travis-ci.community/t/would-like-to-connect-a-repo-to-travis-ci-but-the-github-scope-asks-for-a-lot/1922>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [January 19, 2019, 8:35pm UTC](https://travis-ci.community/t/would-like-to-connect-a-repo-to-travis-ci-but-the-github-scope-asks-for-a-lot/1922 "2019-01-19T20:35:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![emwalker](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/emwalker/32/1014_2.png) [@emwalker](https://travis-ci.community/u/emwalker)\
**Post date:** [January 19, 2019, 8:35pm UTC](https://travis-ci.community/t/would-like-to-connect-a-repo-to-travis-ci-but-the-github-scope-asks-for-a-lot/1922/1 "2019-01-19T20:35:32Z")

</div>

I was looking forward to hooking up Travis CI to a project I have on GitHub, but I decided not to after seeing what was being requested (image below). This is basically the keys to the kingdom, as well as info from GitHub organizations I’m in. What are your plans in this connection? Can you elaborate on why this level of access is needed?

 ![00](https://us1.discourse-cdn.com/flex015/uploads/travis_ci/original/2X/a/acf3ab5734960608297734d4c9cbdee1c3601b1e.png)

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [January 20, 2019, 5:00am UTC](https://travis-ci.community/t/would-like-to-connect-a-repo-to-travis-ci-but-the-github-scope-asks-for-a-lot/1922/2 "2019-01-20T05:00:29Z")

</div>

Judging by [https://github.com/settings/applications](https://github.com/settings/applications) , there’s not one but a whole bunch of different Travis apps (at least, 1 Github app and 3 OAuth apps).

Since I don’t do any work at Github atm, I’ve revoked all authorizations just in case until I need them again.
