Change blog post truncation warning level from 'warn' to 'ignore' in configuration

[Shitanshukumar607]

Description

Change blog post truncation warning
Fixes #582

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify):

Changes Made

Dependencies

• List any new dependencies or tools required for this change.
• Mention any version updates or configurations that need to be considered.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[Copilot]

Pull Request Overview

This PR addresses issue #582 by changing the blog post truncation warning behavior in the Docusaurus configuration. The change modifies the onUntruncatedBlogPosts setting from "warn" to "ignore" to suppress warnings when blog posts don't have truncation markers.

• Changed blog post truncation warning level from "warn" to "ignore"

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[vercel]

@Shitanshukumar607 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[Shitanshukumar607]

I dont know how did this branch got deleted. But its ready to merge

[iitzIrFan]

@Shitanshukumar607 I am requesting changes as we don't want to simply ignore this safety warning here, I want you to inspect the blog section and try to tackle those warning's if, possible as later it can cause broken links issue.

[sanjay-kv]

as @iitzIrFan menitioned we cant do this in prod ready code, the issue underlying with linking of websites. we can find a solution. appreicate bringing this up to PR

[Shitanshukumar607]

okay ill be soon solving it

[sanjay-kv]

I solved it as per the docusaurus documentation in every blog we need to put this truncate before heading starts @Shitanshukumar607