[pull] master from conventional-changelog:master

[pull]

See Commits and Changes for more details.

---

Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[pr-code-reviewer]

👋 Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at [email protected].}}

[instapr]

The pull request looks good overall. I have reviewed the commits and changes and everything seems to be in order. Thank you for your contribution!

Markdown tip: You can use the following syntax to display the sponsor button more prominently:

[pr-explainer-bot]

Pull Request Review - Summary

Hey there! 👋 Here's a summary of the previous tasks and their results for the pull request review. Let's dive in!

Changes

1. Update the package.json file in @commitlint/config-conventional to use the latest version of conventional-changelog-conventionalcommits (6.1.0). 🔄

Suggestions

In cli.test.ts:

• Line 69: Change the URL in the expect statement to 'Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint'.
• Line 78: Change the URL in the expect statement to 'Get help: https://github.com/conventional-changelog/commitlint/#testhelpurl'.
• Line 152: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 168: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 177: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 185: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 194: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 202: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 211: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 219: Change the command in the execa statement to 'git commit -m "test: this should work"'.
• Line 228: Change the command in the execa statement to 'git commit -m "test: this should work"'.

Bugs

In SectionFooter.test.ts:

• Line 68: Update the commit message to use a more descriptive name for the variable isBreaking.
• Line 95: Fix the indentation to align the object properties properly.

In Question.test.ts:

• Line 26: Consider using a more meaningful variable name instead of QUESTION_CONFIG.
• Line 37: Use a more descriptive name for the variable question.
• Line 46: Consider using a more meaningful variable name instead of QUESTION_CONFIG.
• Line 128: Consider using a more descriptive name for the variable question.
• Line 158: Consider using a more descriptive name for the variable question.
• Line 171: Consider using a more descriptive name for the variable question.
• Line 306: Consider using a more descriptive name for the variable question.
• Line 317: Consider using a more descriptive name for the variable question.
• Line 326: Consider using a more descriptive name for the variable question.
• Line 337: Consider using a more descriptive name for the variable question.

Improvements

In cli.ts:

• Line 120: Consider adding a comma after ${pkg.name}@${pkg.version} in the version command.
• Line 204: Consider adding a comma after pkg.name in the CliError constructor.
• Line 249: Consider adding a comma after e in the console.warn statement.
• Line 257: Consider adding a comma after e in the console.warn statement.
• Line 305: Consider adding a comma after opts in the messages.map function.
• Line 361: Consider adding a comma after err in the throw new Error statement.
• Line 395: Consider adding a comma after edit in the throw new Error statement.
• Line 403: Consider adding a comma after edit in the throw new Error statement.

Rating

Please rate the code from 0 to 10 based on the following criteria:

• Readability
• Performance
• Security

Feel free to provide a brief explanation for your rating.

That's it for the summary! If you have any questions or need further clarification, feel free to reach out. Good luck with the pull request! 🚀