My participation in HacktoberFest

[FabianCristancho]

What does this PR do?

Fixes #(issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

• [ ] Test A
• [ ] Test B

Mandatory Tasks

• [ ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my PR needs changes to the documentation
• I haven't checked if my changes generate no new warnings
• I haven't added tests that prove my fix is effective or that my feature works
• I haven't checked if new and existing unit tests pass locally with my changes

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
xprofile	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 6, 2023 7:46pm

[hellofaizan]

Awesome everything seems alright. About to merge

Make sure to drop a ⭐ Star to the repository @FabianCristancho

[FabianCristancho]

Awesome everything seems alright. About to merge

Make sure to drop a ⭐ Star to the repository @FabianCristancho

Ok 👌🏻. Here you have 🫡