If your codebase in TFS has sensitive information (eg. passwords), do not include them in your Azure Devops repository. You can do one of two things: - Remove them from the codebase, check the changed files back into TFS and then be sure to clone the latest code only (step #8). You will lose all history in this case.
- If you clone all history (as in step #9), the passwords will still be available in the repo history. Remove the culprit files from history as follows:
- In the cmd shell, navigate to your repo's folder (in the above example it was c:\tmp\migration\mpdis).
- (See this page for more detail regarding this step). Run the following making sure to change the path-to-the-file to the actual path to the file (eg. src/web.config): git filter-branch --force --index-filter "git rm --cached --ignore-unmatch path-to-the-file" --prune-empty --tag-name-filter cat -- --all
- You've now removed the culprit files from history. You can re-create and add them to the repository later with sensitive information removed if you'd like.
NOTE: If there is a space in a folder name in path-to-the-file, place a slash"\" before the space. E.g. if the path is My Project/Settings.settings, change it to My\ Project/Settings.settings. Otherwise, the above command does not remove specified file. |