We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think various people have already done this in their own forks of bevy_webgl2.
I was wondering if it would make sense to coordinate our efforts?
Perhaps having a bevy-main branch in this repo that works with the latest breaking changes in bevy?
bevy-main
That way, when bevy 0.6 is eventually release, we can just merge the bevy-main branch into main?
main
The text was updated successfully, but these errors were encountered:
If you'd like, you can use the main branch of bevy_webgl2 or my fork
Sorry, something went wrong.
No branches or pull requests
I think various people have already done this in their own forks of bevy_webgl2.
I was wondering if it would make sense to coordinate our efforts?
Perhaps having a
bevy-main
branch in this repo that works with the latest breaking changes in bevy?That way, when bevy 0.6 is eventually release, we can just merge the
bevy-main
branch intomain
?The text was updated successfully, but these errors were encountered: