Documentation

Looking for something in particular?

Commit a Local Test Project to Source Control

Last Modified:

To link a local Test Project to Git, you must first have created a Test Project in Automation. 

You can read more about starting a local Test Project by creating a new project or importing a test project file for more information on how to do this. 

If you are starting from a local repository or remote repository with a project already in source control, please follow those instructions.

Note: Repository markers must match in order for them to be in sync. Be careful to choose the right option to avoid conflicts.

Once you have a Project ready to be linked, right-click on the Project Name in the Navigator, then select Team > Share Project.

The Share Project screen will display, prompting the creation of a local repository. 

Selecting the top checkbox labeled “Use of create repository in parent folder of project” will place the .git folder in the test project folder and is not recommended.  Leaving it unchecked will prompt you for a location.

Note: The .git folder holds all the information necessary for version control and is hidden by default.

Click the Create… Button to create a new repository location on your local machine. 

In the new window, click the Browse… button to search for a location for your repository. Chose a default branch name and click Finish to close the Create a Git Repository window.

Click Finish to continue.

Check the project(s) to be included in your repository to enable the Finish button and click to close to complete the creation of the local repository.

The next step is filling that new repository with your files. Right click on the top level of the test project in the navigator again and select Team -> Commit.

The Git Staging window will open in the bottom right corner by default. You can use the icon in the corner to expand this window to fill the screen or resize the window as necessary.

All files that have been changed since the last commit will appear in the top box labeled Unstaged Changes. Changes must be staged before they can be committed. 

Note: Staging allows changes made for different reasons to be split into different commits. 

Select one or more files and click the single plus sign (➕) to stage selected files. To stage all unstaged files at once, use the stacked plus signs.

Add a clear and concise commit message that describes the changes made and Commit and Push.  

After committing and pushing, there will be a prompt for the Destination Git Repository.

Pasting in the URI will fill in the host, repository path, and protocol. 

  • If you are using HTTPS you will need a Personal Access Token instead of your password. 
  • If you’re using SSH, you’ll need an SSH key. 

Store in the secret store to prevent the need to reenter on each commit/push/pull/sync/etc.

NOTE: When creating GitHub Repository it must NOT be initialized or merging will not work. For Repositories with anything in them, you must pull down from the repo first before creating your test projects or merge files manually to continue!

Click the Preview > button to continue.

Verify the settings and make any changes based on your branching process. Check the box for “Configure upstream for push and pull”. Click the Preview > button to continue.

Confirm your settings are as expected for the push and when ready click the Push button to proceed.

The confirmation box can be closed by hitting the Close button in the bottom right corner.

If you maximized the Git staging window, minimize it back to the corner to continue working.


Feedback

Was this article helpful for you?
Documentation library

Trying to raise a case with our support team?

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top