[DevSecOps] Common GIT Actions in UiPath Studio

About the [DevSecOps] series of tutorials

This series of tutorials will focus on Development, Security and Operations regarding GIT Versioning Systems.
It will cover areas such as:

  • GIT integration
  • Branches & Pull Requests
  • CI/CD (Continuous Integration/Continuous Delivery)
    And much more…

Introduction to this tutorial

This guide will show you some of the most common GIT actions that can be performed directly in UiPath Studio.

The primary benefits of using GIT integration (or any other Version Control System) includes backup of code, transparency in development, collaboration on projects and improved accessability.

I will go through the actions one by one and try to describe its purpose.

To interact with your version control system inside UiPath you can right click your project (or any file) to bring up the contextual menu.
You can also use the menu in the bottom right corner of UiPath Studio.

Popular Version Control Systems include:

  • GitHub
  • Bitbucket
  • GitLab
  • Azure DevOps Server
  • AWS CodeCommit

And many others…

GIT Overview

First off I would like to start with a simple overview of GIT.

Here I have marked where things originate and what the different actions sort-of-do/mean.

Commit & Push

After making changes to code you need to Commit them, in order to “save” the changes in GIT (your local repository).

To “upload” the changes to your remote repository (Version Control System) you should Push the changes.

Commit Message

When committing changes you must define a Commit Message which is a short and precise description of the changes that you have made.

After pushing the changes to your Remote Repository you are able to see the Commit Messages there.

Undo

You are able to Undo changes/additions/deletions made to code before committing them.

After selecting Undo in the contextual menu you are asked to mark the files you would like to revert changes for.

Show Changes

The option to Show Changes displays changes made to a file before you commit them.

This is especially useful when working for longer periods and needing to check up on changes before committing them. But you should generally strive to commit often.

After selecting Show Changes a comparison is displayed.
This shows the latest committed version of the file, alongside the current version.

Here you can see additions marked with green, changes marked with yellow and deletions marked with red.

Show History

Right clicking a file and selecting Show History displays the commits where this file was affected.

The tab Details shows the Commit Message along with information regarding Author and Date.

By selecting the tab Changes you are able to see which files were affected in that commit.

Please let me know if you have any questions or feedback for this tutorial.

Best Regards
Soren

1 Like