Browse Source
# [footer] # ////////////////////////////////////////////////////////////////////////////// # [title.type] # Must be one of the following: # - fix: Commits that fix bugs # - feat: Commits that add new features # - refactor: Commits that change existing code without changing any behavior # - perf: Special refactor commits that improve performance # - style: Commits that do not affect meaning (white-space, formatting, etc.) # - test: Commits that add tests or fixing existing tests # - docs: Commits that affect documentation only # - build: Commits that change build components (scripts, CI pipeline, etc.) # - chore: Miscellaneous commits (modifying .gitignore, etc.) # - tag: Commits for adding tags # # [title.scope] # The scope should be the name of the npm package affected. The following is # the list of supported scopes: # - xa: XAgent (default) # - usi: Unified Storage Interface # - uls: Unified Log System # # [title.summary] # Use the summary field to provide a succinct description of the change: # - Use the imperative, present tense: "change" not "changed" nor "changes" # - Don't capitalize the first letter # - No period (.) at the end # # [body] # Just as in the summary, use the imperative, present tense: "fix" not "fixed" # nor "fixes". # # Explain the motivation for the change in the commit message body. This commit # message should explain why you are making the change. You can include a # comparison of the previous behavior with the new behavior in order to # illustrate the impact of the change. # # [footer] # The footer can contain information about breaking changes and deprecations # and is also the place to reference GitHub issues, JIRA tickets, and other PRs # that this commit closes or is related to. For example: # # Resolves XCAGENT-100 # Resolves XCAGENT-100, SEAL-1500, XCAGENT-512 # # BREAKING CHANGE: <breaking change summary> # <BLANK LINE> # <breaking change description + migration instructions> # <BLANK LINE> # <BLANK LINE> # Resolves <JIRA ticket> # # DEPRECATED: <what is deprecated> # <BLANK LINE> # <deprecation description + recommended update path> # <BLANK LINE> # <BLANK LINE> # Resolves #<JIRA ticket>master
Tom Huang
4 months ago
1 changed files with 16 additions and 16 deletions
Loading…
Reference in new issue