-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not possible to publish to two branches in one project #86
Comments
Just to add, my current workaround is to add an additional subproject and then publish from there. The configuration in the subproject then has to be something like gitPublish {
repoUri = rootProject.gitPublish.repoUri
branch = 'foo'
contents {
from "${rootProject.buildDir}/docs/foo", {
// ...
}
}
commitMessage = "Update FOO for ${project.version}"
}
|
Sure, so some way to configure multiple outputs. Maybe adding a NamedDomainObjectContainer that can cover the settings that are present on the current extension. Leave the existing settings as a proxy for configuring the gitPublish {
// normal top level options
publications {
main {
// same as top level
}
foo {
// options to apply to gitPublishFoo<task>
}
}
} |
See the README for usage details. This is in |
@ajoberstar Thank you. I have finally started using this. It works really well. |
I have a use case where I push to to orphaned branches. Currently this is very hard in the way the plugin is authored. If would be nice is where is some way of adding additional grouping of tasks by convention i.e.
and then configure
and additional tasks are named
gitPublishFooReset
,gitPublishFooCopy
etc.The text was updated successfully, but these errors were encountered: