From e28c876b97665d1ce952582ed973f7e97b465aa2 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 20 Aug 2018 12:09:50 +0200 Subject: [PATCH] Add warning about secrets --- source/_docs/ecosystem/backup/backup_github.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source/_docs/ecosystem/backup/backup_github.markdown b/source/_docs/ecosystem/backup/backup_github.markdown index 278d3fc20cb..2840c5bd628 100644 --- a/source/_docs/ecosystem/backup/backup_github.markdown +++ b/source/_docs/ecosystem/backup/backup_github.markdown @@ -61,8 +61,13 @@ Here is an example that will include your `.gitignore` file, a `scenes` director !.gitignore secrets.yaml known_devices.yaml +.storage ``` +

+ You might read this guide too late and accidentally already have your secrets published. It is not enough to just remove them with a new commit. Git is a version control system and keeps history. You need to delete your repository and start a new one. Also change all passwords and revoke the API keys that were public. +

+ More information on the layout of the file can be found in the [.gitignore manual](https://git-scm.com/docs/gitignore). ### {% linkable_title Step 3: Preparing your Home Assistant directory for GitHub %}