[CI] Allow for a `ux` tag in conventional commits formatting

automl / amltk

A build-it-yourself AutoML Framework

https://automl.github.io/amltk/

BSD 3-Clause "New" or "Revised" License

68 stars 6 forks source link

[CI] Allow for a `ux` tag in conventional commits formatting #188

Closed eddiebergman closed 11 months ago

eddiebergman commented 11 months ago

It's not really a fix to provide a new error message as was done in #187 and some issues are not bugs or features (i.e. #176). It would be good to treat User Experience (UX) as a first class citizen for these cases.

I will add a label for that, however we likely would also like an issue template for it and a conventional commit tag for it, e.g. from the pre-commit:conventional-commits.

eddiebergman commented 11 months ago

Took a look at this and it seems like it's not very trivial and open's up some awkward questions. ux changes are rather vague and could imply a new feature or just a fix, or something that doesn't even warrant a version change on it's own (better error message).

Closing this for now in favour of keeping things simple