Hi, adding my info to the guestbook!

[Amer-css]

Description

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

• 🤝 Add a contributor
• 📝 Documentation Update

Related Issues

Contributors Checklist

I've read through the Getting Started section

• ✅ Yes
• ❌ Not yet

Have you run npm run contributors:generate to generate your profile and the badge on the README?

• ✅ Yes
• ❌ No

Added to documentation?

• 📜 README.md
• 🙅 no documentation needed

Screenshot (Required for PR Review)

[optional] What GIF best describes this PR or how it makes you feel?

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this pull request is meant to address.

Protected Branch

In order to be considered for merging, the pull request changes must not be implemented on the "main" branch.
We would suggest that you close this pull request, create a new branch, implement your changes, and open a new pull request.

Conventional Commit PR Title

In order to be considered for merging, the pull request title must match the specification in conventional commits. You can edit the title in order for this check to pass.
Most often, our PR titles are something like one of these:

• docs: correct typo in README
• feat: implement dark mode"
• fix: correct remove button behavior

Linting Errors

• Found type "null", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"
• No subject found

[adiati98]

Hey @Amer-css,
Thank you for taking on this! We appreciate your contribution. ✨

However, we will close this PR with following reasons:

• You made changes directly on the main branch and we don't allow that. Please refer to this bot warning.

Can you please:

• Create a new branch before working on changes and work on this branch.
• Create an issue and later on, link it to your PR.

Thanks!