Now people will be able to just do go get github.com/xeals/signal-back (or add @latest, @v0.2.0) like the old times (starting with Go 1.12) and get the required binary release with proper dependencies.
By design repo should now also tag the signal/vX.Y.Z releases of the signal autogenerated submodule, so that other people could use it without dragging the whole binary with it.
This will in turn allow doing go get github.com/xeals/signal-back/signal (or with version suffix like with the binary).
If this gets merged, I suggest tagging the merge commit with 2 tags:
As asked in https://github.com/xeals/signal-back/pull/42 I separated module-related changes from the linter fixes.
Now people will be able to just do
go get github.com/xeals/signal-back(or add@latest,@v0.2.0) like the old times (starting with Go 1.12) and get the required binary release with proper dependencies.By design repo should now also tag the
signal/vX.Y.Zreleases of thesignalautogenerated submodule, so that other people could use it without dragging the whole binary with it. This will in turn allow doinggo get github.com/xeals/signal-back/signal(or with version suffix like with the binary).If this gets merged, I suggest tagging the merge commit with 2 tags:
v0.2.0for the repo itselfsignal/v0.1.0for the submodule