Skip to content

Conversation

@donnamware
Copy link
Contributor

@donnamware donnamware commented Dec 1, 2025

Description

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

  • ☝️ Add a pizza fact or trivia
  • 🧑‍🍳 Add a pizza recipe
  • 🗺️ Add a regional pizza
  • 🍴 Add a traditional food
  • 📝 Documentation Update

Related Tickets & Documents

Added to documentation?

  • 📜 README.md
  • [x ] 🙅 no documentation needed

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

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 "Relates to #XYZ" where XYZ is the issue number that this PR 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 "Contribution", must be one of "feat","fix","docs","style","refactor","perf","test","build","ci","chore","revert"

@adiati98
Copy link
Collaborator

adiati98 commented Dec 1, 2025

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

However, we will close this PR with following reasons:

  • You made the changes directly on the main branch, and we don't allow that.

Please create a new branch to work on your changes and a new PR.
Also, kindly refer to these bot warnings to avoid failed checks for your next PR.

Let me know if you have questions or need help. Thank you!

@adiati98 adiati98 closed this Dec 1, 2025
@donnamware
Copy link
Contributor Author

Thank you for steering me in the right direction. I will create a new branch and submit my changes. I'll also go over the bot warnings.

I am looking forward to getting my submission completed without any problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants