trial

[hrsut]

Description

Include a description of the change done

Why

The motivation for the change (if applicable)

How

How the change is implemented (if it's not self evident in the diff)

Close: #XXX

Checklist:

Before submitting this PR, please make sure:

• I am complying with the contributing doc
• My code builds clean without any errors or warnings
• I have added/extended tests that prove my fix is effective or that my feature works
• I have made corresponding changes to the documentation, and it builds correctly

[github-actions]

Pull request title linting 🚨

In order to merge this pull request, the title of the pull request should be prefixed by one of the available types.

Available types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

---

Examples

feat(grpc): add new endpoint
refactor: combine class A and class B
ci: update pull request linter
style: change format of strings

💁 For more examples, visit https://www.conventionalcommits.org/en/v1.0.0/#examples.