Don't worry, if you can't fix the problem with the PR title, a person who takes care of things will handle it. We use [Conventional Commits](https://www.conventionalcommits.org/) specification for adding human and machine readable meaning to commit messages. The expected PR title formatting is: `<type>(<scope>): <description>` where `(<scope>)` declaration is optional and `<type>` must be one of the following: - build: Changes that affect the build system, external dependencies, CI configuration - chore: Routine maintenance that does not change engine behavior - docs: Documentation only changes - feat: A new feature - fix: A bug fix - other: Changes that don't belong to other categories - perf: A code change that improves performance - refactor: A code change that neither fixes a bug nor adds a feature - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - test: Adding missing tests or correcting existing tests