docs: Add information about PR with unassigned issue to the contributing guidelines

[DevJSter]

Description :

fixes : Added information about PR with unassigned issue to the contributing guidelines #251
changes done In the docs/contributing/introduction-to-contributing.md:
Changes

Part 1

• Remove the first paragraph and replace with:

  ---
  We actively welcome your pull requests. However, you must ensure that **you are assigned** to an existing issue before working on changes, and you need to **link your work to the issue** in your PR form.
  ---
  

Part 2

• In the second bullet point of point no. 9, remove the <br /> and the following sentence.

  - - Unsolicited code is welcomed, but an issue is required to announce your intentions. <br /> **_PRs without a linked issue will be marked invalid and closed_**.
  + - Unsolicited code is welcomed, but an issue is required to announce your intentions.

• After point no. 9, before [!IMPORTANT], add this copy:

  ⚠️ **PRs will be marked as invalid and may be closed if:**
  
  - the issue is not assigned to the contributor who opened the PR
  - no issue is linked to the PR
  

Part 3

• Change the format of the word "IMPORTANT" as below:

  - > [!IMPORTANT]
  + > **IMPORTANT:**

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

Fixes #251

Mobile & Desktop Screenshots/Recordings

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

Added to documentation?

• 📜 README.md
• 📓 docs.opensauced.pizza
• 🍕 dev.to/opensauced
• 📕 storybook
• 🙅 no documentation needed

[netlify]

👷 Deploy request for docs-open pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	c7dbf63

[github-actions]

PR Compliance Checks Passed!

[adiati98]

Hi @DevJSter,
Thank you for your PR! 🙌

I left a review here for you to fix before we can merge your PR.

Also, please put the issue number in the "Related Tickets & Documents" section on the PR form, and use this format Closes #000.

Let me know when it's fixed and ready for a review.
Thank you. 🙂

[DevJSter]

Hey @adiati98 , I've done the changes you told me to !!
this is how it looks in the production(locally)

[adiati98]

Hi @DevJSter,

Thank you for the prompt change!
The fix is exactly what we want. 👍

However I just noticed that you also made change in the package.json file, which we don't want to have.
I left the review for you to fix.

Also, please take a look at the GitHub bot in this PR.
There, you can see the warnings and information on how to make your PR compliance to our contributing guidelines.

Please let me know once you fixed these. And let me know if you have any questions or help. Thank you!

[adiati98]

Well done, @DevJSter! 🙌
Thank you for the changes!

FYI, I made the edit to the "Related Tickets & Documents" section in your PR form to meet the compliance requirement of our contributing guidelines. Please see how it supposed to be written for your future reference. You can read more about linking a PR to an issue in this GitHub docs. 👍

If you haven't, you can join our community Discord. 😊

Also, check out our pizza-verse repo if you want to contribute further! 🍕

[github-actions]

🎉 This PR is included in version 1.64.0 🎉

The release is available on:

• GitHub release
• ghcr.io container (@latest dist-tag)

Your semantic-release bot 📦🚀