Closed konstin closed 8 months ago
Thank you! This looks good. When CI is green I will be happy to merge.
Can you elaborate on how you hit this error? I'm surprised a higher level / user facing check didn't catch the bug.
(The commit message needs to follow "conventional commit" before I can merge.)
(The commit message needs to follow "conventional commit" before I can merge.)
Nah, it's fine you rename the commit anyway when merging so you can conventionalize it @Eh2406
@mpizenberg how can I check that the new message will make CI happy. I have messed up before and ended merging with a bad name and had red CI on dev, witch required doing a force push to fix, witch required turning off the branch protection. Witch is a mess I don't want to repeat.
Ahah, ok makes sense ^^
commitlint passes locally, though i don't know if it matches the CI one.
Can you elaborate on how you hit this error? I'm surprised a higher level / user facing check didn't catch the bug.
iirc i was midway into refactoring that made more versions available (those with only a source distribution and lacking a wheel) in on place but not in another.
Accidentally caused this error, added a better debug message