![]() ![]() Configuring Git in PowerShell Studio or PrimalScriptĪfter installing Git, you will need to set up Git source control in PowerShell Studio or PrimalScript. ![]() Under the Source Control section, select General: Then select the Source Control tab at the bottom: In PowerShell Studio, on the Home ribbon in the Windows section, select Options (or File > Options). Under Universal Version Control System select Git.In the Options > Source Control section of either SAPIEN editor: ![]() In PowerShell Studio, the Git menu is in the Source Control ribbon tab: In PrimalScript, the Git menu is in the Tools ribbon tab:Īll options in the menu are preset Git commands. There are two additional options if you want to do more with Git: Showing both the GUI and Git Shell Prior to cloning an existing repositoryįirst, a placeholder for the cloned repository needs to exist on the local machine. For this example, I created an empty folder named GitRepoPowerShellScripts01. Now I can proceed to clone my Git repository from my Azure DevOps site. Push the changes back to the remote repository.Commit the changes in the local repository.Working with Git is as simple as following the SDLC (Software Development Life-Cycle): Keep in mind that I have previously set my permissions to access this repository. Note: The Git menu options are enabled when a script is open in the editor. This option is used to copy the remote repository to the local drive, and it will prompt for the following information:Ĭloning first prompt Cloning second prompt When the cloning process completes, the source code will be available for editing. ![]() Now I can open a script and start making changes to the code. This option gives a list of the changes made to the code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |