-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
[Suggestion] Store resources as submodule #13
Comments
Thats something I was going to do in the next version of ossos, but hopefully have a set of models I made myself so I dont need to worry about copyrights & whatnot. |
I think you can still make it a submodule regardless (put a disclaimer in the README about copyrights if needed). I made a PR for ossos_next: |
The ossos_next branch now includes this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, setting up this project for local testing requires going into
examples/_res
and following the instructions to clone the resources repository. This can be problematic because:main
branch of the repository is not guaranteed to be in sync with commits in this repositoryThis could be handled more elegantly with the resources repo as a Git submodule of this project.
This would mean that:
git clone --recurse-submodules
The text was updated successfully, but these errors were encountered: