Browse files

Add migration notice for existing deploy keys.

  • Loading branch information...
1 parent 08cc260 commit b1bd2cfd08a5e32ad2c3a91434a493518fe4b17f @roidrage roidrage committed Jul 26, 2012
Showing with 6 additions and 0 deletions.
  1. +6 −0 blog/_posts/
@@ -41,6 +41,12 @@ That way we don't break existing projects that still have a .travis.yml
configured and still allow for you to specify a key in the .travis.yml if you
need to.
+If you're already using Travis Pro and have your deploy key set up in the
+.travis.yml, there's an easy way to migrate. Just delete the `source_key` from
+the .travis.yml and remove it from the GitHub deploy keys as well. We'll
+automatically generate a new SSH key for your repository the next time you push
+a commit.
Curious about Travis Pro? You can still donate to our [Love
campaign]( to get on the fast track to using it before
we launch it to the public! If you donated, just hit us up on

0 comments on commit b1bd2cf

Please sign in to comment.