You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
This is a GitHub Action that ensures your PR title matches the [Conventional Commits spec](https://www.conventionalcommits.org/). The typical use case is to use this in combination with a tool like [semantic-release](https://github.com/semantic-release/semantic-release) to automate releases.
4
4
5
-
Used by: [Apache](https://github.com/apache/pulsar) · [Vercel](https://github.com/vercel/ncc) · [Microsoft](https://github.com/microsoft/SynapseML) · [Firebase](https://github.com/firebase/flutterfire) · [AWS](https://github.com/aws-ia/terraform-aws-eks-blueprints) · [Electron](https://github.com/electron/forge) – and many more.
5
+
Used by: [Apache](https://github.com/apache/pulsar) · [Vercel](https://github.com/vercel/ncc) · [Microsoft](https://github.com/microsoft/SynapseML) · [Firebase](https://github.com/firebase/flutterfire) · [AWS](https://github.com/aws-ia/terraform-aws-eks-blueprints) · [Electron](https://github.com/electron/forge) – and [many more](https://github.com/amannn/action-semantic-pull-request/network/dependents).
6
6
7
7
## Examples
8
8
@@ -12,14 +12,14 @@ Used by: [Apache](https://github.com/apache/pulsar) · [Vercel](https://github.c
12
12
- refactor!: Drop support for Node.js 12
13
13
- feat(ui): Add `Button` component
14
14
15
-
Note that since PR titles only have a single line, you have to use `!` to indicate breaking changes.
15
+
> Note that since PR titles only have a single line, you have to use `!` to indicate breaking changes.
16
16
17
17
See [Conventional Commits](https://www.conventionalcommits.org/) for more examples.
18
18
19
19
## Installation
20
20
21
21
1. If your goal is to create squashed commits that will be used for automated releases, you'll want to configure your GitHub repository to [use the squash & merge strategy](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests) and tick the option "Default to PR title for squash merge commits".
22
-
2.[Add the action](https://docs.github.com/en/actions/quickstart) with the following configuration
22
+
2.[Add the action](https://docs.github.com/en/actions/quickstart) with the following configuration:
0 commit comments