ktmud commented on pull request #12754: URL: https://github.com/apache/superset/pull/12754#issuecomment-767374159
The prefixes are task types. "Breaking change" sounds more like a flag or label. [Conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#specification) specifies breaking changes starts with `!`, or include `BREAKING CHANGE:` in the footer. E.g. ``` refactor!: drop support for Python 3.6 ``` or ``` refactor!: drop support for Python 3.6 BREAKING CHANGE: as discussed in #xxxx, Python 3.6 is no longer supported. ``` I think it'd be worthwhile following the best practices from the community. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
