Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 6ca156a

Browse files
docs(contributing): fix typo and enhance conclussion
1 parent 73795ce commit 6ca156a

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

‎CONTRIBUTING.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,7 @@ Semantic commits are a way of writing commit messages that follow a standardized
7777
A semantic commit consists of three main parts:
7878

7979
1. **Commit type**: Indicates the type of change made. Common commit types include:
80+
8081
- :sparkles: feat: Introduces a new feature.
8182
- :bug: fix: Fixes a bug.
8283
- :wrench: chore: Project maintenance tasks, such as dependency updates.
@@ -89,7 +90,7 @@ A semantic commit consists of three main parts:
8990

9091
3. **Description**: A brief description of the change made. It should be clear, concise, and understandable to anyone reading the project history.
9192

92-
## Example of a semantic commit 💡
93+
## Examples of semantic commits 💡
9394

9495
```bash
9596
feat(parser): add ability to parse arrays
@@ -108,7 +109,6 @@ security(auth): Fixed security vulnerability in authentication process
108109

109110
This commit introduces a new feature to the parser, which is the ability to parse arrays.
110111

111-
112112
## Tools for semantic commits 🛠️
113113

114114
There are several tools that can assist you in writing semantic commits, such as:
@@ -120,9 +120,9 @@ There are several tools that can assist you in writing semantic commits, such as
120120
## Additional resources i️
121121

122122
- [Complete guide to semantic commits](https://www.conventionalcommits.org/es/v1.0.0-beta.2/)
123-
- [How to write commit messages](*URL removed as it is invalid*)
124-
- [Best practices for writing commits in Git](*URL removed as it is invalid*)
123+
- [How to write commit messages](_URL removed as it is invalid_)
124+
- [Best practices for writing commits in Git](_URL removed as it is invalid_)
125125

126126
## Conclusion 🎉
127127

128-
Semantic commits are a simple and effective way to improve the readability and understanding of your project's history. I recommend starting to use them in your projects to take advantage of all their benefits.
128+
Semantic commits are a simple and effective way to improve the readability and understanding of your project's history. We encourage you to start using them in your projects to take advantage of all their benefits.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /