maxmustermann/PowerShell
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update mapping.md

Browse source 
Add a note to use source-depot branch for initial adding [skip ci]
This commit is contained in:
Sergei Vorobev 2016-04-06 11:37:39 -07:00
parent bb8ed24b86
commit 1560809147
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/workflow/mapping.md
View file

@ -40,6 +40,8 @@ If you are bringing new (that are not yet included) files from source-depot, you
This way, we can keep track of changes and have ability to integrate changes back to Source Depot. This way, we can keep track of changes and have ability to integrate changes back to Source Depot.
We will use term **integrate** for that kind of new files. We will use term **integrate** for that kind of new files.
* Use `source-depot` branch to initially add files.
* Make a separate commit with update for `mapping.json`. Separate commit will help to manage this change in other branches. * Make a separate commit with update for `mapping.json`. Separate commit will help to manage this change in other branches.
* You can use `Copy-SubmoduleFiles` function to copy files on disk. * You can use `Copy-SubmoduleFiles` function to copy files on disk.
@ -51,6 +53,8 @@ Use `--author="PowerShell Team <PowerShellTeam@hotmail.com>"` switch to indicate
git commit --author="PowerShell Team <PowerShellTeam@hotmail.com>" git commit --author="PowerShell Team <PowerShellTeam@hotmail.com>"
``` ```
* Merge changes to `master`
Use this approach for **test files** as well. Use this approach for **test files** as well.
You can add them under `test` directory and include in CI test run, but keep the notion of integration in `mapping.json`. You can add them under `test` directory and include in CI test run, but keep the notion of integration in `mapping.json`.