Thanks for the PR,@yf-yang!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	3b6693d
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/6557239fef541a000788bd2c
😎 Deploy Preview	https://deploy-preview-7706--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 89 (🔴 down 9 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify site configuration.

☁️ Nx Cloud Report

CI is running/has finished running commands for commitae66a81. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

Sent with 💌 fromNxCloud.

Btw, the Netlify failures are unrelated to this PR. You should be able to ignore them.

Just curious 👀 , you are using squash and merge option, so only the PR title should follow conventional commit guidelines, the commit messages don't matter, right?

so only the PR title should follow conventional commit guidelines, the commit messages don't matter, right?

That's right. You can do whatever you want with commit titles and commit as many times as you want.