Skip to content

Commit fd51b5e

Browse files
authored
Merge branch 'main' into tm-fastify-404
2 parents 9ed84de + b39c96c commit fd51b5e

File tree

24 files changed

+992
-1386
lines changed

24 files changed

+992
-1386
lines changed

.commitlintrc.yml

Lines changed: 0 additions & 29 deletions
This file was deleted.

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# CHANGELOG
22

3-
All notable changes to this project will be documented in this file. Do not remove the "Unreleased" header; it is used in the automated release workflow.
3+
As of v0.25.1 (2022-01-24) changelog content has moved to separate CHANGELOG.md files for each package. Use [this search for a list of all CHANGELOG.md files in this repo](https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-js-contrib+path%3A**%2FCHANGELOG.md&type=code).
44

55
## Unreleased
66

CONTRIBUTING.md

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -42,16 +42,9 @@ for general practices for OpenTelemetry project.
4242

4343
#### Conventional commit
4444

45-
The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. You can see examples [here](https://www.conventionalcommits.org/en/v1.0.0-beta.4/#examples).
46-
We use [commitlint](https://github.com/conventional-changelog/commitlint) and [husky](https://github.com/typicode/husky) to prevent bad commit message.
47-
For example, you want to submit the following commit message `git commit -s -am "my bad commit"`.
48-
You will receive the following error :
45+
The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. You can see examples [here](https://www.conventionalcommits.org/en/v1.0.0/#examples).
4946

50-
```text
51-
✖ type must be one of [ci, feat, fix, docs, style, refactor, perf, test, revert, chore] [type-enum]
52-
```
53-
54-
Here an example that will pass the verification: `git commit -s -am "chore(opentelemetry-core): update deps"`
47+
We use [the "pr-title" CI workflow](./.github/workflows/pr-title.yml) to ensure PR titles, and hence the commit message from those PRs, follow the Conventional Commits spec.
5548

5649
### Fork
5750

0 commit comments

Comments
 (0)