Best practices for UiPath Studio -> Git/GitLab integration: Branches vs Separate Projects?

I’m in the process of populating a new GitLab repository with about 200 UiPath scripts that we have.

Our scripts tend to be small and in the past we grouped them together under one project. However, we found this became unwieldy as time went on, especially managing branches to avoid conflicts between development and ongoing maintenance.

Would it be better to create a separate project for each script? It seems more logical and flexible, the downside being the need to create 200 new projects.

I searched for any guidance on this but came up empty. Can anyone offer some clarity?

Is there any way you can group them ?
Instead of 200 if you can group them based on your implementation
For example some script will be for ui
Some will be for database

PS I am assuming they are not runtime dependent on each other

If they are dependent than accordingly you can create
And maintain the document with the info of every brach contains

1 Like

Good suggestion! That certainly cuts down on the number of projects. Thank you.

Thank you :blush: if it was helpful kindly mark the answer as solution so it will be helpful to other community member , thanks ! :smiling_face:

@yosemitesam

Ideally maintaining them separate would be a good option to have automatic pipelines when code is check in etc…

If all of those is not needed then grouping them as @jast1631 mentioned also makes sense

Another way is to group them based on function …HR,Supply chain etc

Cheers

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.