Skip to content

Validate commit messages and branch naming convension #6

@sinke237

Description

@sinke237
  1. add and validate commit message
    • very commit has be signed.
    • commit format: <type>(<scope>): <message> or <type>: <message>
  2. introducee branch naming convension for open source practices. e.g <feature|setup|bugfix|infra|ci|test|docs|deploy|security|perf|refactor|upgrade>/issue-<issue_number>-<description_text>
  3. Prevent direct push to the develop and main branches

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status

Ready

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions