Commit List showing as empty only in shared folders

Feedback Studio
, ,
1

When trying to commit changes to GitLab, the ‘changes’ (pencil icon) shows as having 43 uncommitted changes, but when those changes are attempted to be committed, the error message is returned as an EmptyCommitException.

I’m using Studio Enterprise version 2022.10.14, and this error only occurs on a shared folder in my company. Would obviously like to use this drive for collaboration…

The initial commit works, but after is still showing changes when there are none! If we do make any changes to the code, the commit list correctly adds the number of changes to the counter on the footer panel, but when you try and commit those, the commit list then comes up as completely empty with no option to commit and push!!

Hope someone can help :slight_smile:

3

@oliver.golding

First things thats the same reason its not advised to use shared folders

Try from local it should be working

And git commits are done for the same collaboration ..then why do we need a shared folder again?

Cheers

1 Like
4

Noted, will develop from the local folders. Thanks Anil.

1 Like
5

@oliver.golding,

When studio modify/compile/debug the code, it generates lines if temporary files. When the code is on shared drive, this will result in folder locked by previous execution.

So it’s good practice to develop the code on local drive and avoid shared drive.

1 Like
6

Many thanks! Will share with my wider team.

1 Like
7

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