Skip to content
This repository was archived by the owner on Jul 6, 2025. It is now read-only.

Commit f318f83

Browse files
committed
Remove Commit Message
1 parent 030d716 commit f318f83

File tree

1 file changed

+0
-32
lines changed

1 file changed

+0
-32
lines changed

CONTRIBUTING.md

Lines changed: 0 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -48,38 +48,6 @@ deno test -A --unstable --location=http://0.0.0.0 --import-map=./import_map.json
4848
- **/server** server code
4949
- **/shared** shared code
5050

51-
## Commit Message Guidelines
52-
53-
We have very precise rules over how our git commit messages can be formatted. This leads to **more
54-
readable messages** that are easy to follow when looking through the **project history**.
55-
56-
### Commit Message Format
57-
58-
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
59-
format that includes a **type**, a **scope** and a **subject**:
60-
61-
```
62-
<type>(<scope>): <subject>
63-
<BLANK LINE>
64-
<body>
65-
<BLANK LINE>
66-
<footer>
67-
```
68-
69-
The **header** is mandatory and the **scope** of the header is optional.
70-
71-
Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
72-
to read on GitHub as well as in various git tools.
73-
74-
Footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
75-
76-
Samples:
77-
78-
```
79-
docs(changelog): update change log to 0.0.9
80-
```
81-
82-
8351
## Code of Conduct
8452

8553
All contributors are expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).

0 commit comments

Comments
 (0)