add warning about renaming

rosieyohannan · rosieyohannan · commit b251b762de88 · 2020-05-19T19:32:26.000+01:00
diff --git a/jekyll/_cci2/gh-bb-integration.md b/jekyll/_cci2/gh-bb-integration.md
@@ -65,6 +65,17 @@ Integrated status also appears on the pull request screen, to show that all test
     3. Regenerate the keys in CircleCI project.
 - Ensure no developer has access to a build in a repo with a User Key that requires more access than they have.
 
+## Renaming Orgs and Repositories
+
+If you find you need to rename an org or repo that you have previously hooked up to CircleCI, best practice is to follow these steps:
+
+1. Rename org/repo in VCS
+2. Head to the CircleCI application, using the new org name
+3. Confirm that your plan, projects and settings have been transferred successfully
+4. You are then free to create a new org/repo with the previously-used name in your VCS, if desired.
+
+**Note**: If these steps are not followed, it is possible, although rare that you may lose access to your org or repo settings, including **environment variables** and **contexts**.
+
 
 ## Enable Your Project to Check Out Additional Private Repositories
 
