-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cannot export if using version control to manage releases #11
Comments
Workaround:
|
Is your unity-package-tools/Unity/Assets/JCMG/PackageTools/Scripts/Editor/Tools/FileTools.cs Line 240 in 279c92d
|
[EDIT: this comment is not relevant, see next comment] A little more info on this. The .git folder was a red herring. It is also happening in a devtest publication folder in which I am not version controlled. Here the error is Looks like Are you using Windows Subsystem for Linux? I'm wondering if this is some kind of wierd permissions problem based on that (I am using it, so knowing if you are using it or not will help in debugging). I'm on a deadline right now, but I'll try to debug this soon. The workaround of manually deleting is OK for now. |
The second issue is unrelated. This happens if you put the package manifest descriptor in the directory containing the project being packaged, moving them back to the Asset folder root fixed it. The first problem, with .git folder still exists, I've not had time to debug yet, I'm still using the above workaround |
In a new project this issue is not occurring. I believe it may be an oddity with that specific project and windows file locks |
Describe the bug
My release process involves a
release/stable
branch maintained in Git. In order to create a release I checkout this branch into a separate location and have package-tools export the source into this directory. But this throws the error below. This error is because it is trying to delete the .git directory - which is not desired.Unity Version:
Unity 2019.4.15f1
To Reproduce
I have an open source project which makes it easy to reproduce step by step instructions at
https://github.com/TheWizardsCode/DevLogger#release-process
Expected behavior
The
DevLogger-Release
folder contains the correct package and I cangit add .
,git commit -m "release v 0.2.5"
,git push
Additional context
I think I can probably work around this by force pushing to the repo. I will test this out and post a workaround if it works. However, it may be simpler if .git files were not deleted. What do you think?
Should I work on a patch?
The text was updated successfully, but these errors were encountered: