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
Novu currently lacks a commit linting system. Implementing Commit Lint in our project can significantly improve the quality of commit messages, making it easier for both contributors and team members to understand the nature of contributions. This proposal outlines the benefits and steps required to set up Commit Lint in Novu.
π€ Why is this feature needed ?
Improved commit message quality.
Better organization of version history.
Enhanced collaboration and understanding among contributors.
Facilitates tracking and reviewing changes.
βοΈ How do you aim to achieve this?
Step 1: I will Install Commit Lint
Step 2: Create a commitlint.config.js file in the project root with the following content to use the conventional commit convention:
Step 3: Add a pre-commit hook to automatically run Commit Lint before each commit. This ensures that commit messages adhere to the convention consistently.
Step 4: Adding contributors to writing meaningful and well-structured commit messages. Emphasize the use of a clear type (e.g., feat, fix, chore) and a concise subject line.
π Feature description
Novu currently lacks a commit linting system. Implementing Commit Lint in our project can significantly improve the quality of commit messages, making it easier for both contributors and team members to understand the nature of contributions. This proposal outlines the benefits and steps required to set up Commit Lint in Novu.
π€ Why is this feature needed ?
βοΈ How do you aim to achieve this?
Step 1: I will Install Commit Lint
Step 2: Create a
commitlint.config.js
file in the project root with the following content to use the conventional commit convention:Step 3: Add a pre-commit hook to automatically run Commit Lint before each commit. This ensures that commit messages adhere to the convention consistently.
Step 4: Adding contributors to writing meaningful and well-structured commit messages. Emphasize the use of a clear type (e.g., feat, fix, chore) and a concise subject line.
ποΈ Additional Information
Conventional Commits: https://www.conventionalcommits.org/en/v1.0.0/
Commit Lint: https://commitlint.js.org/
π Have you spent some time to check if this feature request has been raised before?
π’ Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: