Search Issue Tracker
Won't Fix
Votes
3
Found in
Issue ID
1215815
Regression
No
[VCS] Provider operations should allow working on files outside of project
VersionControl.Provider operations (checkout, add, ...) today only work on paths that are known to the asset database & are versioned.
In large productions, it's very common to have more than "just the unity project" in the source control. And they probably want to build some in-editor tooling that would allow their content creators to interact with the assets source files from within Unity: Opening source files, checking them out, etc. Would be nice if Provider APIs would handle paths outside of project.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Based on team resourcing, available workarounds (using the VCS client external to Unity), and the age of the request, we are not going to deliver this feature.