Added "HACKTOBERFEST.md" to welcome contributors and promote best practices.

[SachinRajakaruna]

Summary

This PR introduces a new HACKTOBERFEST.md file designed to welcome Hacktoberfest participants and guide them toward contributing effectively and respectfully.
The document aligns with the repository’s tone, coding conventions, and contribution standards.

Why This Adds Value?

• Provides clear guidance for new contributors joining during Hacktoberfest.
• Encourages thoughtful, high-quality pull requests instead of spam or low-effort contributions.
• Reinforces the existing contribution and code style guidelines, ensuring consistency.
• Adds a positive, community-focused touch to the project’s documentation.

Key Points

• This addition supports both maintainers and contributors by making the onboarding process easier, clearer, and more consistent; especially during Hacktoberfest when new participants join.
• I hope this small contribution helps strengthen the community around it. 💚

-Thank you for maintaining this great project! Happy Hacktoberfest!

[github-actions]

🎉 Thanks for your first pull request! The team will review it shortly. We’re excited to have you contribute!

[Copilot]

Pull Request Overview

This PR adds a new HACKTOBERFEST.md file to welcome Hacktoberfest contributors and provide guidance for effective participation. The document aims to encourage high-quality contributions while setting clear expectations for new contributors during the Hacktoberfest event.

• Introduces comprehensive contribution guidelines specifically for Hacktoberfest participants
• Establishes best practices for Git workflow and community interaction
• Provides clear examples and expectations to reduce low-quality contributions

---

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

[Copilot]

The title should use proper markdown heading syntax. Consider using '# 🎉 Welcome to Hacktoberfest!' instead of plain text.

Suggested change

	🎉 Welcome to Hacktoberfest!
	# 🎉 Welcome to Hacktoberfest!

[Copilot]

This should use proper markdown heading syntax. Consider using '## 💡 How You Can Contribute?' and remove the question mark for better grammar.

Suggested change

	💡 How You Can Contribute?
	## 💡 How You Can Contribute

[Copilot]

This should use proper markdown heading syntax. Consider using '## ✅ Recommended Git Practices:' for consistency.

Suggested change

	✅ Recommended Git Practices:
	## ✅ Recommended Git Practices:

[Copilot]

This should use proper markdown heading syntax. Consider using '## 🤝 Community Spirit:' for consistency.

Suggested change

	🤝 Community Spirit:
	## 🤝 Community Spirit:

[Copilot]

This should use proper markdown heading syntax. Consider using '## 🌟 Thank You!' for consistency.

Suggested change

	🌟 Thank You!
	## 🌟 Thank You!

[Copilot]

The list items should use proper markdown list syntax with dashes (-) or asterisks (*) instead of manual indentation for better rendering and accessibility.

Suggested change

	You can take part in many helpful ways:
	Improve or clarify documentation.
	Add small but meaningful examples that help new users.
	Report and fix bugs with clear, reproducible steps.
	Review open pull requests and provide constructive feedback.
	Suggest small enhancements that improve usability or code clarity.
	Before opening a new pull request or issue, please review the existing discussions to avoid duplication.
	---
	✅ Recommended Git Practices:
	To keep contributions clear and easy to review:
	Use small, focused commits with descriptive messages.
	Follow the existing naming and code style conventions.
	Sync with the latest main branch before creating a pull request.
	Keep your PRs concise and relevant to one improvement at a time.
	Add a short summary explaining the purpose of your change.
	Example commit format:
	docs: clarify setup instructions in README
	---
	🤝 Community Spirit:
	Hacktoberfest is about collaboration, learning, and shared progress.
	Be respectful, patient, and kind in all interactions. We value thoughtful contributions over volume, and we’re happy to support you if you’re contributing for the first time.
	---
	🌟 Thank You!
	Your contribution helps make Notion SDK for .NET more reliable and easier to use for everyone.
	We’re grateful for your time, care, and effort — and we look forward to reviewing your pull request.
	Happy contributing and happy Hacktoberfest! 💚
	You can take part in many helpful ways:
	- Improve or clarify documentation.
	- Add small but meaningful examples that help new users.
	- Report and fix bugs with clear, reproducible steps.
	- Review open pull requests and provide constructive feedback.
	- Suggest small enhancements that improve usability or code clarity.
	Before opening a new pull request or issue, please review the existing discussions to avoid duplication.
	---
	✅ Recommended Git Practices:
	To keep contributions clear and easy to review:
	- Use small, focused commits with descriptive messages.
	- Follow the existing naming and code style conventions.
	- Sync with the latest main branch before creating a pull request.
	- Keep your PRs concise and relevant to one improvement at a time.
	- Add a short summary explaining the purpose of your change.
	Example commit format:
	- docs: clarify setup instructions in README
	---
	🤝 Community Spirit:
	- Hacktoberfest is about collaboration, learning, and shared progress.
	- Be respectful, patient, and kind in all interactions. We value thoughtful contributions over volume, and we’re happy to support you if you’re contributing for the first time.
	---
	🌟 Thank You!
	- Your contribution helps make Notion SDK for .NET more reliable and easier to use for everyone.
	- We’re grateful for your time, care, and effort — and we look forward to reviewing your pull request.
	- Happy contributing and happy Hacktoberfest! 💚

[Copilot]

These list items should use proper markdown list syntax with dashes (-) or asterisks (*) instead of manual indentation for better rendering and accessibility.

Suggested change

	You can take part in many helpful ways:
	Improve or clarify documentation.
	Add small but meaningful examples that help new users.
	Report and fix bugs with clear, reproducible steps.
	Review open pull requests and provide constructive feedback.
	Suggest small enhancements that improve usability or code clarity.
	Before opening a new pull request or issue, please review the existing discussions to avoid duplication.
	---
	✅ Recommended Git Practices:
	To keep contributions clear and easy to review:
	Use small, focused commits with descriptive messages.
	Follow the existing naming and code style conventions.
	Sync with the latest main branch before creating a pull request.
	Keep your PRs concise and relevant to one improvement at a time.
	Add a short summary explaining the purpose of your change.
	You can take part in many helpful ways:
	- Improve or clarify documentation.
	- Add small but meaningful examples that help new users.
	- Report and fix bugs with clear, reproducible steps.
	- Review open pull requests and provide constructive feedback.
	- Suggest small enhancements that improve usability or code clarity.
	Before opening a new pull request or issue, please review the existing discussions to avoid duplication.
	---
	✅ Recommended Git Practices:
	To keep contributions clear and easy to review:
	- Use small, focused commits with descriptive messages.
	- Follow the existing naming and code style conventions.
	- Sync with the latest main branch before creating a pull request.
	- Keep your PRs concise and relevant to one improvement at a time.
	- Add a short summary explaining the purpose of your change.

[KoditkarVedant]

Hey, thanks so much for contributing this Markdown file! 😊

Just a quick note — Hacktoberfest is a yearly event, and sometimes repositories choose to opt out of it. If that happens, this file might end up being removed later, which wouldn’t be ideal.

Also, since we already follow a general contribution guideline, this file ends up being a bit redundant.

That said, we’d love to have your help on other things! Feel free to check out any of the open, unassigned issues, report new issue — you’re more than welcome to jump in.

Thanks again for your time and enthusiasm! 💪