john-tipper
john-tipper
I have pushed a PR (#46) that I believe fixes this (hope it will be merged soon), please let me know if you see further issues.
I have pushed a PR (#46) that I believe fixes this (hope it will be merged soon), please let me know if you see further issues.
I'm in a similar position to @31i0t, please consider merging this PR.
For me, the concrete use case I wish to use this feature for is in resolving multiple accounts for complicated cross-account deployments. We have a lot of AWS Organization accounts,...
I've gone through what the Java plugin does to resolve this and I think we can at least support incrementing the version across dependent modules. Here's what I propose, covering...
I have managed to come up with a working implementation. It differs in implementation somewhat from the description above, in that I discovered that the version incrementing is performed by...
I have addressed this issue in PR #326.
Coveralls seems to be complaining about lack of tests in `DummyRepository`, which is a class that does nothing and doesn't seem sensible to test. Please let me know what you...
I have found that when there are large numbers of submodules (50+) and Gradle builds in parallel, the creation of the release tags causes contention on the Git repo and...
@sradi, please may I ask how your monorepo is set up? Is it a Gradle multi-module build, where each module has a configuration section like the below, or are you...