Changes for page git-for-windows
Last modified by Gideon Lombard on 2023/09/18 11:37
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -g it-for-windows1 +getting-started - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -technical-documentation.Source Control. client-tools.WebHome1 +technical-documentation.Source Control.WebHome - Content
-
... ... @@ -1,3 +1,18 @@ 1 +Hi Team 2 + 3 +**Pre-requisites** 4 + 5 +~1. Install [[WinMerge>>https://winmerge.org/]] 6 + 7 +2. Install [[Notepad++>>https://notepad-plus-plus.org/]] 8 + 9 +3. Install [[VisualStudio Code>>https://code.visualstudio.com/Download]] 10 + 11 +When you open the projects from the new locations you might have to fix some of the references due to the folder structures changing ie code is not under a "Development" folder as it now is branch based. This can be done by editing the csproj directly or doing a search and replace with the new paths where applicable, alternatively you can remove the old references via IDE and relink to new paths **do not link to old paths on your machine**. 12 + 13 + 14 +Some of the projects have been converted to start using our own nuget feed so to ensure you do not have any connectivity issues: 15 + 1 1 ~1. Make sure that you download and install the latest version of Git from [[https:~~/~~/gitforwindows.org/>>https://gitforwindows.org/]] 2 2 3 3 ... ... @@ -4,7 +4,7 @@ 4 4 [[image:1657114851784-392.png]] 5 5 6 6 7 - Keepalltheoptions as perthedefault.22 +Leave all settings as per default on this screen. 8 8 9 9 [[image:1657114877100-308.png]] 10 10 ... ... @@ -39,3 +39,90 @@ 39 39 40 40 41 41 [[image:1657115106191-233.png]] 57 + 58 + 59 + 60 + 61 + 62 +1. make sure your VS is updated with the latest updates (critical) 63 +1. ((( 64 +install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link 65 + 66 +[[image:1657111373296-938.png]] 67 + 68 +Click the copy icons to copy the text 69 + 70 +[[image:1657111476063-780.png]] 71 + 72 + 73 +Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window 74 + 75 +[[image:1657111556824-350.png]] 76 + 77 + 78 +[[image:1657111596157-325.png]] 79 + 80 +Click the Run button to execute the script 81 + 82 + 83 +))) 84 +1. ((( 85 +For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator 86 + 87 +dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev 88 +))) 89 + 90 +1. 91 + 92 +1. 93 + 94 +Also while we in the transition phase it might be helpful to add this link via this command: 95 + 96 +>mklink /D c:\dev\src\Packages C:\dev\Packages 97 + 98 + 99 +[[image:1657115475686-934.png]] 100 + 101 + 102 +The URL's for different repositories to clone is as follows: 103 + 104 + ~-~-> Application Source Code 105 + 106 +[[image:1657115603808-846.png]] 107 + 108 + 109 +[[image:1657115842929-756.png]] 110 + 111 +For reference attached is the mappings of the new folders from old folders. 112 + 113 + 114 +If you want to start making changes follow the following process: 115 + 116 + 117 +1. ((( 118 +Right click the migration folder and create a new branch via the TortoiseGit menu 119 + 120 + 121 +1. [[image:image-20220706143954-1.png]] 122 +))) 123 +1. specify branch name follow this pattern for now (names cannot have spaces use dashes -): 124 + 125 +1. feature/il-12345 126 +11. if it is issue log related you can add a -short-description if needed 127 +11. 12345 = replace with issue log number 128 +1. feature/12345 129 +11. if it is azure task related 130 +11. 12345 = replace with az workitem number 131 +1. feature/short-description 132 +11. if it has no work item associated to it 133 + 134 +1. make sure you select branch = master and switch to new branch is checked 135 +11. [[image:image-20220706143954-2.png]] 136 + 137 +As mentioned Friday if there is a piece of new code that has sync over yet and you need it, merge it over on your end with something like winmerge //once you have created a feature branch//. 138 + 139 + 140 +As always please reach out if you get stuck. 141 + 142 + 143 +Regards