How do you manage to do some code reviews in studio projects

[Matt67 (Matthieu LEVAL)]

Hello, I want to implement more “enterprise grade” things in my company,
and when I was a C# developer we managed to have frequent code reviews within visual studio. We are able to have a look at all changes made by a colleague, append some comments etc… validate / reject.

How do you manage to do this on your end ? From my knowledge there isn’t a functionnality like this in studio. More, when having conflits during pulls, it is not the best interface and user friendly experience to see updates and see what have changed. More if you update studio and default sequence are changing etc…

I will appreciate a lot your feedbacks about this

Thanks

[Michael.Vornes]

Hi @Matt67
In my experience I would say it’s better to use traditional git approach (not directly from studio) but using cmd or git gui directly in the project folder. And then you can create the traditional DevOps structure, creating pipelines and using pull request. But even in this structure who will perform the code review will need to have studio and download the project (git pull) and then can approve/reject the pull request and also make comments.

[SorenB]

Hello @Matt67

Studio offers GIT integration so you could do the review part in a GIT Versioning System such as Bitbucket, GitHub, GitLab or other.

Personally we use Jira for Issue/Bug tracking, which is then integrated into Bitbucket for creation of branches, and subsequent pull requests with the Review “built in”.

Perhaps take a look at my series of tutorials for inspiration:

[DevSecOps] Connect a UiPath project to a GitHub repository

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… DevSecOps Series Connect a UiPath Project to a GitHub repository From GitHub Issue to Merging a Pull Request Introduction to this tutorial This guide will show you how to connect a UiPath projec…

[DevSecOps] From GitHub Issue to Merging a Pull Request

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… DevSecOps Series Connect a UiPath Project to a GitHub repository From GitHub Issue to Merging a Pull Request Introduction to this tutorial This guide will show you how to go from: A GitHub Iss…

Regards
Soren

[Eric_Alvarado]

Hi @Matt67
Code Review is a big topic, that can be approached in various ways. Here are some insights:

1-Code Review excel file (Basic): Utilize an Excel file where findings can be logged, and developers can respond with comments and evidence of resolution for new automations. For code changes, developers should document the modifications made, allowing you to provide feedback.

2-UiPath is introducing “Bookmarks” – a feature that enables you to add comments directly in UiPath Studio. UiPath Community 2024.2 Release

3. Orchestrator Compare Functionality: Navigate to Processes, select the required process, go to Explore Package, and click the ‘Compare’ button (next to the ‘Packages’ version label). Choose the new version and the previous one to compare. This will highlight workflows with changes; then, you will be able to navigate over all the code changes made and even analyzed activity properties changes.

Note: This feature is only available for Processes, not libraries.

4. For libraries, consider exporting the workflow as an Excel file (both old and new versions) to compare them. The Excel file will show you activities, logic, elements, properties, selectors, targeting methods, etc.

[Matt67 (Matthieu LEVAL)]

Thanks for all your answers and insights ! I will take a look at every input received. I like the new Bookmarks function integrated into studio, will see how far I can go with this