# GitHub repository moved but Travis CI didn't?

**URL:** <https://travis-ci.community/t/github-repository-moved-but-travis-ci-didnt/8247>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** github\
**Created:** [April 20, 2020, 11:36am UTC](https://travis-ci.community/t/github-repository-moved-but-travis-ci-didnt/8247 "2020-04-20T11:36:28Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [April 21, 2020, 3:04pm UTC](https://travis-ci.community/t/github-repository-moved-but-travis-ci-didnt/8247/4 "2020-04-21T15:04:31Z")

</div>

From what I can see at

> **[Build software better, together](https://github.com/orgs/community/discussions/)**
>
> GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

> **[Webhooks documentation - GitHub Docs](https://docs.github.com/en/webhooks)**
>
> Webhooks can let your integrations take an action in response to events that occur on GitHub.

it’s impossible for a 3rd-party service, including Travis, to know when a repository is moved because there’s no notification for that.

Neither is it possible to automatically set up integration at the repo’s new location because Travis needs a brand new permission grant for the new organization to be able to do anything on its behalf.

* * *

So, set up the integration anew as per below.  
It’s possible that this won’t be needed if Github was smart enough to update webhooks appropriately when moving – then you will see that the integration is already enabled after registering at Travis with the new organization. (Still, it won’t hurt to reset everything just in case.)

> [@Pushes won't trigger new builds anymore after the project has been inactive for a long time](https://travis-ci.community/t/pushes-wont-trigger-new-builds-anymore-after-the-project-has-been-inactive-for-a-long-time/5716/2):
>
> Most probably, Travis webhook changed in these 10 months in a backward-incompatible way (I do remember topics that suggest so: [GitHub services to Webhooks migration update](https://travis-ci.community/t/github-services-to-webhooks-migration-update/2079), [No new builds being triggered](https://travis-ci.community/t/no-new-builds-being-triggered/185), [Double builds for all merges and PRs](https://travis-ci.community/t/double-builds-for-all-merges-and-prs/2316/2)). So you need to: Disable CI for the project in [https://travis-ci.org/account/repositories](https://travis-ci.org/account/repositories) Look through Webhooks and Integrations & services in Github project’s settings and delete anything Travis-related Re-enable CI for the project

---

_[View the full topic](https://travis-ci.community/t/github-repository-moved-but-travis-ci-didnt/8247)._