tag:help.appveyor.com,2012-11-13:/discussions/problems/19513-migrating-configurationAppVeyor: Discussion 2019-03-24T21:00:50Ztag:help.appveyor.com,2012-11-13:Comment/468496782019-01-22T00:17:55Z2019-01-22T00:17:55ZMigrating configuration<div><p>Is the second project title marked with <code>PRIVATE</code> tag?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/468496782019-01-22T07:35:24Z2019-01-22T07:35:24ZMigrating configuration<div><p>Hello,</p>
<p>Both project are private</p>
<p>[cid:<a href="mailto:part1.2335325D.46016296@blackfire.io">part1.2335325D.46016296@blackfire.io</a>]</p>
<p>[cid:<a href="mailto:part2.5E531E29.BEDAD7B7@blackfire.io">part2.5E531E29.BEDAD7B7@blackfire.io</a>]</p>
<p>On 22/01/2019 01:17, Owen McDonnell wrote:</p></div>Romain Neutrontag:help.appveyor.com,2012-11-13:Comment/468496782019-01-22T20:41:50Z2019-01-22T20:41:50ZMigrating configuration<div><p>GitHub authorization for older account <code>fabpot</code> it set up using OAuth, while for new one <code>FabienPotencier</code> with GitHub Apps. More details on GitHub Apps are <a href="https://www.appveyor.com/blog/2018/10/02/github-apps-integration/">here</a>, including this:</p>
<p><em>With GitHub App repository webhooks and deploy (SSH) keys stay untouched. Instead of adding a deploy (SSH) key to the repo the App uses an “installation” token for cloning the repo via HTTPS. That installation token is rotated hourly. To start new builds on push and pull requests, AppVeyor App uses a centralized webhook handler which is called by all app-enabled repos.</em></p>
<p>You can change GitHub authorization for <code>FabienPotencier</code> account at <a href="https://ci.appveyor.com/account/FabienPotencier/authorizations">Authorizations settings</a> if needed.</p></div>Ilya Finkelshteyn