Closed chippmann closed 2 years ago
Maybe you can directly target master
, as develop
branch is going to die with 3.5
release.
Maybe you can directly target
master
, asdevelop
branch is going to die with3.5
release.
But isn't this going to be merge beforehand and would then be merged directly together with the 3.5 changes?
Maybe you can directly target
master
, asdevelop
branch is going to die with3.5
release.But isn't this going to be merge beforehand and would then be merged directly together with the 3.5 changes?
This would do less to review when merging develop in master if we merge this directly to master
Maybe you can directly target
master
, asdevelop
branch is going to die with3.5
release.But isn't this going to be merge beforehand and would then be merged directly together with the 3.5 changes?
This would do less to review when merging develop in master if we merge this directly to master
true will do that
I'm trying to get started with Godot and #346 is bugging me. Looks like this can be merged?
I'm trying to get started with Godot and #346 is bugging me. Looks like this can be merged?
@travisfw If it's urgent to you, you can build the plugin yourself and install it locally from disk: https://www.jetbrains.com/help/idea/managing-plugins.html#install_plugin_from_disk
To build the plugin:
git clone git@github.com:utopia-rise/godot-kotlin-jvm.git
cd godot-kotlin-jvm/kt
./gradlew :godot-intellij-plugin:assemble
kt/plugins/godot-intellij-plugin/build/distributions
Our next release should not be far away though. After #344 is merged (i still need to do the linux testing), we can probably do a release.
Resolves #346, resolves #345 and resolves #347.