Documentation says “haxelib git” can address a branch in a remote repo. However, if I have reasons to worry that future changes in that branch may break my code, what should I do? A solution which comes to my mind immediately is to include external lib as a git submodule and do “haxelib dev”, but maybe there’a a different way?
AFAIR you can specify a commit instead of a branch for haxelib git
1 Like
Yeah you can checkout a commit hash instead of branch. See this for exact syntax.
1 Like
There is no commit hash example in documentation, maybe it works like that