Skip to content

docs: add @km-wahid as a contributor#923

Closed
km-wahid wants to merge 1 commit into
OpenSource-Communities:mainfrom
km-wahid:main
Closed

docs: add @km-wahid as a contributor#923
km-wahid wants to merge 1 commit into
OpenSource-Communities:mainfrom
km-wahid:main

Conversation

@km-wahid
Copy link
Copy Markdown
Contributor

@km-wahid km-wahid commented Mar 8, 2026

Description

This PR adds @km-wahid as a contributor to the project.
I have added my contributor profile and generated the contributor badge on the README using the npm run contributors:generate command.

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

  • 🤝 Add a contributor
  • 📝 Documentation Update

Related Issues

Closes #XXX

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)

Screenshot 2026-03-08 at 23 06 10

A screenshot showing my contributor profile generated on the README has been attached.

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

Excited to contribute to this open source project! 🚀

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 8, 2026

Congratulations on completing the How to Contribute to Open Source chapter of the Intro to Open Source Course with your contribution to this repository, @km-wahid! You're almost to the end of the course!

Copy link
Copy Markdown

@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 "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.

Copy link
Copy Markdown

@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.

Congratulations on submitting your first Pull Request! 🎉

We appreciate your contribution. Feel free to join the conversation in our
Community and say hello!

@adiati98
Copy link
Copy Markdown
Collaborator

adiati98 commented Mar 9, 2026

Hey @km-wahid,
Thank you for your contribution. ✨

However, we're closing 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.

Please create a new branch before working on changes and create a new PR. Also, when creating a PR, you must link the issue number in the "Related Issue" section on your PR. You can find the number next to your issue's title.

@adiati98 adiati98 closed this Mar 9, 2026
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