-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs(website): fix heading level inconsistencies #4320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for the PR, @Josh-Cena! 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 on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
❌ Deploy Preview for typescript-eslint failed. 🔨 Explore the source changes: 62f86e2 🔍 Inspect the deploy log: https://app.netlify.com/sites/typescript-eslint/deploys/61bff25cf019fb00075183ec |
This looks quite problematic (also in other PRs). I can't see why the build fails |
67b8090
to
f0dd0fe
Compare
no need to bother with merging main into your branch - we can keep track of what gets merged and merge for you if it's required before landing the PR :) |
Yeah, just getting bored & hitting the "update" button🙈 Hope it doesn't get confusing |
Meanwhile I still have no clue about the failing Netlify build... |
That's on our end.. we need to fix our build step. |
PR Checklist
Overview
Make the TOC more consistent and easier to navigate