Skip to content

Commit 24e6064

Browse files
author
dharapandya85
committed
docs: enforce conventional commits use and remove redundant line
Signed-off-by: dharapandya85 <[email protected]>
1 parent 824ad62 commit 24e6064

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Thank you for your interest in contributing to `patch-hub`! This document outlin
66

77
1. [Code of Conduct](#code-of-conduct)
88
2. [Getting Started](#getting-started)
9-
3. [Development Workflow](#development-workflow)
9+
3. [Development s](#development-workflow)
1010
4. [Coding Style](#coding-style)
1111
5. [Commit Guidelines](#commit-guidelines)
1212
6. [Pull Request Guidelines](#pull-request-guidelines)
@@ -119,9 +119,6 @@ Commit contents, in other words, the changes the commit introduce should:
119119
Example:
120120
feat(foo)!: introduce breaking change bar
121121
122-
`patch-hub` follows the use of [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) wherein you indicate the type of change you're making at the start with a label, followed by a scope (optional, since the project is still small), and then the commit message after a colon. In case the commit is a breaking change, i.e it disrupts existing functionality, please use the `!` symbol before the `:` to indicate as such.
123-
124-
125122
Example Commits:
126123
- Breaking change that introduces a feature to `config`: `feat(config)!: allow provided config object to extend other configs`
127124
- Bug fix to patch parsing logic: `fix(patch): fix incorrect title in patches`

0 commit comments

Comments
 (0)