Support adding a new/private file to source control about blender-uvcs HOT 3 CLOSED

I'm not sure I understand the issue correctly.

When a new .blend file is created under a PlasticSCM workspace, and you open it with Blender, you can use the "Pending changes" section to perform the checkin.

Note we are asking plastic to do so by using the parameters --all and --private

from blender-uvcs.

Coming from Perforce, I tend to tidy up my workspace very carefully:

• I keep Private files around that are not meant to be checked in (not yet at least) eg local tests or modifications meant for another branch etc
• I explicitly Checkout (or add to source control) the file intended to be checked-in
• I use local Changelists to help sort these two groups; Changelists only support assets that are "in source control" (not private files) which is perfect for my way of working described above :)

It's the first issue I encountered when I tried to use the plugin for the first time; I couldn't tell how to add the blend file to source control in order to be able to check it in. It's only after looking at all the other options that I found that I could check it in nevertheless. So it might be worth considering.

From what I saw with other VCS and other tools/IDE, it's quite common that the plugin automatically call the "add" operations when creating new files (eg in Visual Studio)

I agree that it's low priority though :)

Cheers!

from blender-uvcs.

Good point, adding it as an enhancement 👍🏻

from blender-uvcs.