-
Notifications
You must be signed in to change notification settings - Fork 2
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
changelogPush double pushes tags and fails #24
Comments
Can you provide a stacktrace for the failure? I haven't seen this before, but I have had hiccups converting a legacy project to spotless-changelog where I had tags lying around from before the conversion. |
Sure: Stacktrace
|
Okay, so it's failing here Lines 82 to 85 in 01b0419
It seems that the tag does in fact exist, so it should fail, yes? Why are you running |
and it fails with:
But as described before the refs were logged to be pushed correctly. And I can also verified that they indeed have arrived correctly online as: release/0.2.2 |
Is it possible that Also, |
No I think the problem is related to the first thing! It indeed is not a composite build, but rather a multi-module project. Currently, I have applied the spotless-changelog indeed to all sub-projects. Let me try to see if it is working fine when only adding it to the root. |
Indeed. That is working. Many thanks. |
There needs to be a one-to-one mapping from |
Why does a:
configured spotless-changelog (which should be pretty much the defaults fails for:
with:
after logging:
which successfully shows that:
But why is it somehow trying to push it a 2nd time?
The text was updated successfully, but these errors were encountered: