Git Commit Message Standard

Mon, 01 Jan 0001 00:00:00 +0000

Format

# [Header] <type>(<scope>): :emoji: <subject>
# - type: feat, fix, perf, refactor, style, revert, docs, test, ci,
#         chore, milestone, release, revision, alpha, beta, rc
# - scope: can be empty
# - subject: a verb-led phrase, no trailing period
# - header occupies exactly one line
# - each line must not exceed 72 characters (Chinese characters count as 2)
#
# [Body] description
# - why is this change needed?
# - how was the problem diagnosed?
# - what are the side effects of this change?
# - each line must not exceed 72 characters (Chinese characters count as 2)
#
# [Footer] <token:> <text>
# - issue ID or link
# - BREAKING CHANGE
# - each line must not exceed 72 characters (Chinese characters count as 2)

Reference: https://www.conventionalcommits.org/

Branch and Version Number Standard

Mon, 01 Jan 0001 00:00:00 +0000

Version Number

Starting from V3.0.0, XWOS follows the Semantic Versioning specification:

Version format: MAJOR.MINOR.PATCH, with the following increment rules:
- MAJOR version: when incompatible API changes are made, also known as a milestone version.
- MINOR version: when backward-compatible functionality is added, also known as a stable version.
- PATCH version: when backward-compatible bug fixes are made.

Branches

main branch: the main branch.
Version number branches: branches for stable versions and milestone versions.

Standards on XWOS

Git Commit Message Standard

Format

Branch and Version Number Standard

Version Number

Branches