How to migrate to the new GitHub Integration

As part of our continued commitment to bring people joy in managing your team's development efforts, we've made some behind-the-scenes work toward updating our GitHub integration.

Migration to the new integration is required and is not automatic. New customers setting up the GitHub integration for the first time will not need to do anything differently, but existing customers currently in the old integration will need to authorize the new integration by May 1, 2020.

Authorizing the new Integration

From your Clubhouse workspace, click on the user icon in the top right.

  1. Click Integrations
  2. Locate and click on the GitHub integration
  3. In the yellow pop-up message, click the Authorize button.

mceclip0.png

What's new about this latest VCS integration?

You will not notice any immediate difference to your current integration; all features you're accustomed to stay the same. However, this new integration will allow us to better build upon more features to bring you more joy. 😀

What happens if I don't migrate to the new integration by May 1, 2020?

Your current integration will cease to work properly if you do not migrate by May 1, 2020. This means VCS events like Pull Requests or Branch merges will not be processed by Clubhouse and stories will not be affected. However, you can easily migrate after this date manually by following the aforementioned steps.