You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using GitVersioning to determine the version of my sbt project. I'm having a problem with a submodule though. I'm using a tagged commit (on the master branch) from a different git repository. Since the release, new commit have been added to the master branch.
Now, git reports that my working directory is clean (for both my main repo and the submodule's repo). However, due to the fact that submodule's in a detached HEAD state the version of my project is appended with -SNAPSHOT.
Any idea on how I could solve this (short of overriding the version manually)?
The text was updated successfully, but these errors were encountered:
Otherwise, I think we're having multiple issues with projects containing git submodules or more than one git repo (like #97). I don't think anyone really thought carefully about those kind of projects, and it's time that we do.
Hi,
I'm using
GitVersioning
to determine the version of my sbt project. I'm having a problem with a submodule though. I'm using a tagged commit (on the master branch) from a different git repository. Since the release, new commit have been added to the master branch.Now, git reports that my working directory is clean (for both my main repo and the submodule's repo). However, due to the fact that submodule's in a detached HEAD state the version of my project is appended with
-SNAPSHOT
.Any idea on how I could solve this (short of overriding the version manually)?
The text was updated successfully, but these errors were encountered: