Branch&Commit Message Naming Policy
=

## Pull Request

- Description

## Description
- [] what you done A
- [] what you done B

## Note
- Some dependency, or the things that used to notidy the reviewer
- note for yourself for this PR

- not too much commit in one PR
- Merge with Squash (Optional)

## Branch Name

- Category: `feat`, `fix`, `refactor`, `test`, `docs`
- "/"
- Description: This description should be short and "kebab-cased".
- Lower case only
- '-'(minus), not '_' (bottom line)
- [Reference](https://dev.to/varbsan/a-simplified-convention-for-naming-branches-and-commits-in-git-il4)

### Example

feat/r17
fix/pdu-release
refactor/oauth-token-ctx
test/charging-ci
docs/chf-design

#### Others: blog

blog/ims-intro

## Commit Message

[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

- Commit message with ! to draw attention to breaking change
- prefixed with a type, which consists of a noun, `feat`, `fix`, etc.
- Must contain **<type>** and **<description>**
- Types (others than these are also allowed)
- fix
- feat
- build
- chore
- ci
- docs
- style
- refactor
- perf
- test

### Example

feat: allow provided config object to extend other configs

chore!: drop support for Node 6

docs: correct spelling of CHANGELOG