Repository configurations

remote-release-notes/images/1_47/repoconfigpathssetting.png

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e792e4908a41f03427d1094b4800fd94931ceaf776ad49df1364261ca48d9cb
+size 32742

remote-release-notes/v1_47.md

@@ -16,8 +16,18 @@ When opening a Git repository folder the "Reopen in Container" notification now
 
 ![Reopen in Container notification](images/1_47/reopenincontainernotification.png)
 
+The "Reopen in Container" notification is also shown when there is a configuration in our [vscode-dev-containers](https://github.com/microsoft/vscode-dev-containers/tree/master/repository-containers) repository matching the current folder's Git repository.
+
 If you choose `Don't Show Again` you are now asked if you want to not see this notification only for the current folder or for any folder. If you later want to see it again you can now reset it for all folders with `F1` > `Remote-Containers: Reset Don't Show Reopen Notification`.
 
+### Configurable Repository Configuration Paths
+
+There is now a setting for adding local lookup paths for configurations to repositories. The folder structure at the lookup paths is `<host>/<owner>/<repository>` (e.g., `github.com/angular/angular`). See the [vscode-dev-containers](https://github.com/microsoft/vscode-dev-containers/tree/master/repository-containers) repository for examples.
+
+![Reopen in Container notification](images/1_47/repoconfigpathssetting.png)
+
+[Stuart Leeks (@stuartleeks)](https://github.com/stuartleeks) contributed this setting as a PR.
+
 ### Attach configuration by container name
 
 In addition to having configuration files per Docker image, we now also support configuration files per container name. To create one first attach VS Code to a running container and then create a configuration for its name with `F1` > `Remote-Containers: Open Named Container Configuration File`.