Documentation

Looking for something in particular?

Automation V3: Commit a Local Test Project to Source Control

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.

Creating a Local Repository

Once you’re ready to share your project, you’ll start by creating a local repository. This creates the framework for Git to synchronize with. 

Visit the Git option on the Action Bar and select the Git Repositories tab.

Select the link to Create a new local Git repository.

Next, define a location for your repository. It’s common practice to keep the repository with your test project, so we’ve selected the test project location here.

If you are unsure of where your test project is located, use the hamburger menu to select the Test Project Properties and copy the location. If you do this, you’ll have to remove the \tests folder at the end of the location to get to the root of your project. 

Click Create.

Now you’ll see all the files listed in the repository tab, ready to sync.

Staging and Committing Changes

The next step is syncing your files to a remote repository.

Go to the Git Staging tab.

You’ll find all the files ready in the Unstaged Changes section.

Use the double plus to stage all the changes so they are ready for synchronization. Only staged files will be synced.  Add a commit message.

Click Commit and Push. You’ll receive an error stating that the repository can’t be found. Click Ok.

Click the new Push HEAD button. A modal window will appear prompting for the remote repository information. 

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. 

Check the Store in the Secure Store box to prevent the need to reenter on each commit/push/pull/sync/etc.


NOTE: When creating a remote Repository on Github or Gitlab 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.


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