docs: add conventional commits guide

[Bashir3355]

Added documentation referencing Conventional Commits to the Practicum Wiki to guide students on writing standardized commit messages.

Includes:

• Link to the official Conventional Commits specification
• Explanation of why standardized commit messages are important
• Examples of common commit types such as feat, fix, and docs

Fixes #45

[Bashir3355]

documentation added and looks good.
Waiting for the approval to be completed or merged.

[DS-0277]

The description looks great. Good job!

[josehorta21]

Reviewed the PR. The Issue Creation Guide content itself is well-written —
clear purpose section, step-by-step instructions, and a useful Best Practices
section at the end.

However, I noticed a mismatch between the PR metadata and the actual file
changes: the PR title says "docs: add conventional commits guide" and the
description references Conventional Commits (with examples like feat, fix,
docs), but the only file added in this PR is Issue-Creation/Issue-Creation.md,
which is an Issue Creation guide — not a Conventional Commits guide.

Could you clarify whether:

1. The Conventional Commits file was meant to be included but is missing, or
2. The PR title and description should be updated to reflect that this adds
   the Issue Creation Guide instead?

Also noticed the failing checks (Auto-assign and Sync Project Status). Once
the title/content alignment is sorted out, this should be ready to go.

Content LGTM, just needs the metadata cleaned up.

[DennizGarza1234]

Reviewed the PR. The documentation is well structured and easy to follow.

The setup steps are clear and logically ordered. Code changes align with the PR description and are easy to understand.

One suggestion: ensure that the PR title matches the exact content of the files being changed to avoid confusion during review.

Overall, this looks good and meets the expected requirements.

[ErmiyasHailemichael]

Good effort on this guide! A few things I noticed:

• The PR title says "conventional commits guide" but the content is actually an Issue Creation guide — these don't match.
• The wiki already has an Issue Creation page with more detail. This version is missing some sections like naming conventions and sprint assignment.
• Small grammar fix needed: "Provide screenshots or examples this will be helpful" should be "Provide screenshots or examples if applicable."

Worth aligning with the existing wiki page before merging to avoid confusion.

[ErmiyasHailemichael]

• The PR title says "conventional commits guide" but the content is actually an Issue Creation guide — these don't match.
• The wiki already has an Issue Creation page with more detail. This version is missing some sections like naming conventions and sprint assignment.
• Small grammar fix needed: "Provide screenshots or examples this will be helpful" should be "Provide screenshots or examples if applicable."