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
Hi, I use this for publishing maven packages, and it usually works great, so thank you! But now I need to create a new repo from another existing repo, and I would like to publish the old releases that are way behind the master branch.
When I try locally, it just hangs forever. When I use GitHub actions it attempts to merge into master and fails when there is a merge conflict.
So basically, can I configure it to work the same as standard maven publishing if the release is outdated, without retroactively reverting back to standard gradle publishing?
The text was updated successfully, but these errors were encountered:
Hi, I use this for publishing maven packages, and it usually works great, so thank you! But now I need to create a new repo from another existing repo, and I would like to publish the old releases that are way behind the master branch.
When I try locally, it just hangs forever. When I use GitHub actions it attempts to merge into master and fails when there is a merge conflict.
So basically, can I configure it to work the same as standard maven publishing if the release is outdated, without retroactively reverting back to standard gradle publishing?
The text was updated successfully, but these errors were encountered: