Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,1 +1,1 @@
1		-Technical Documentation.Source Control.migration.WebHome
	1	+technical-documentation.Source Control.migration.WebHome

Content

...	...	@@ -1,7 +1,13 @@
	1	+= Overview =
	2	+
	3	+
1	1	We will migrate all the tfvc repos into one git repository called "migration" as a staging area to facilitate the process of moving the individual solutions into its final git location. This can be done in a delta fasion until we restrict the tfvc repos and everyone starts working off the git staging repo.
2	2
3	3	Feature branches can be merged back into master via a pull request and the feature branches that are not applicable anymore can be abandoned.
4	4
	8	+= Migration process =
	9	+
	10	+
5	5	The process to sync the tfvc to the git repo
6	6
7	7	1. pull all the latest changes from TFVC via cli
...	...	@@ -27,3 +27,16 @@
27	27	11. an .gitignore gets injected this will make sure binaries are excluded
28	28	11. subsequent runs if the repo already exists will create a feature branch for the main branches timestamped with the date is was ran
29	29	ie: /feature/master-20220202-172700
	36	+
	37	+
	38	+= Disable TFVC repository =
	39	+
	40	+After a repository has been moved to the staging environment and a call has been made to switch off the old repository we will put the old repository in read-only mode, the steps are:
	41	+
	42	+1. Notify the team and request that any pending changes need to be committed
	43	+1. Do a final delta migration of the repository
	44	+1. Disable inheritance on the repository
	45	+1. Remove Contributors group
	46	+1. Make sure the Readers group is present
	47	+
	48	+