-
Notifications
You must be signed in to change notification settings - Fork 447
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
Add UPM package distribution option #962
Comments
It's also confusing to have the plugin itself show up in changes, it has a lot of binary files that you wouldn't normally want to commit. |
Hey @tlaedre @nickmccurdy thanks for letting us know what you need. Ultimately this is a direction we would like to explore, but we don't have any immediate plans to start with it. @nickmccurdy I agree it's confusing, but it shouldn't constantly be showing changes, only after an update or when changing versions of Unity. Is that what you are seeing? |
I recently reinstalled Unity to get the latest version and then installed the GitHub extension, and it shows up in changes every time I launch this Unity project. |
You should be free to commit the changes, that is the intention. |
Hey there! 1- Would com.github.unity be the right package name? |
@JoNax97 Hey! This work is already underway at https://github.com/Unity-Technologies/Git-for-Unity, and I'm planning on porting that back here this week. If you want to try it out, the master branch over there is already usable as a package, you can try the sample project in the |
#1070 has all the changes needed for this, early builds are available in https://ci.appveyor.com/project/shana/git-for-unity |
This project is not maintained anymore. The replacement is Git for Unity, at https://github.com/spoiledcat/git-for-unity. If you have GitHub for Unity in your project, remove it first and then install the Git for Unity package, see the README in the link for instructions. |
It would be great if there was a distribution option to get Github4Unity as a upm package. There's no real reason for the tool to live inside the Assets/ folder.
The text was updated successfully, but these errors were encountered: