GitHub-Achievements icon indicating copy to clipboard operation
GitHub-Achievements copied to clipboard
verified publisher icon drknzz

Update README.md

Open meralhamarat opened this issue 1 year ago • 8 comments

##Adding "Discussion Answerer" Badge

Changes Made:

  • Added the "Discussion Answerer" badge to the README.md file.

Why:

I added the "Discussion Answerer" badge to showcase my active engagement in project discussions. I believe that participating in discussions is a valuable contribution to the community and enhances the collaborative atmosphere of the project.

How:

I followed the established GitHub workflow:

  1. Forked the repository.
  2. Cloned the forked repository to my local machine.
  3. Made the necessary changes to the README.md file.
  4. Committed the changes with a meaningful commit message.
  5. Pushed the changes to my fork on GitHub.
  6. Opened this pull request to propose the changes to the original project.

Additional Information:

I am committed to continuing my active involvement in discussions and contributing to the growth of the project. I appreciate the opportunity to showcase this badge as a symbol of my dedication to community engagement.

Thank you for considering my contribution.

Best regards, Meral Hamarat

meralhamarat avatar Dec 27 '23 17:12 meralhamarat

Mmmh! I suppose we were on the same page regarding the addition of the discussion highlight badge. 😅 😊

rezzcode avatar Dec 28 '23 10:12 rezzcode

Mmmh! I suppose we were on the same page regarding the addition of the discussion highlight badge. 😅 😊 Haha, yes, that's right. I hope my contribution gets accepted soon, and I receive feedback 😬. Good luck to you too.

meralhamarat avatar Dec 28 '23 11:12 meralhamarat

Adding "Discussion Answerer" Badge Changes Made:

Added the "Discussion Answerer" badge to the README.md file. Why: I included the "Discussion Answerer" badge to highlight my ongoing commitment to actively engage in project discussions. I firmly believe that participating in discussions not only strengthens community bonds but also fosters a collaborative atmosphere essential for project success.

How: Here's the step-by-step process I followed as part of the established GitHub workflow:

Forked the repository. Cloned the forked repository to my local machine. Implemented the necessary changes to the README.md file. Committed the changes with a meaningful commit message. Pushed the changes to my fork on GitHub. Opened this pull request to propose the changes to the original project. Additional Information: In addition to the badge addition, I plan to:

Actively contribute to ongoing discussions. Continue enhancing the project through meaningful interactions and code contributions. Explore opportunities to further support the project's growth. I am enthusiastic about showcasing the "Discussion Answerer" badge as a symbol of my unwavering dedication to community engagement.

Thank you for considering and acknowledging my contribution.

joaquimtimoteo avatar Dec 29 '23 16:12 joaquimtimoteo

Haha, yes, that's right. I hope my contribution gets accepted soon, and I receive feedback 😬. Good luck to you too.

Good luck on your end too. thanks

the1Riddle avatar Dec 31 '23 08:12 the1Riddle

unfortunately, the badge is no longer available to be earned 🥲

the1Riddle avatar Feb 25 '24 19:02 the1Riddle

Mmmh! I suppose we were on the same page regarding the addition of the discussion highlight badge. 😅 😊 Haha, yes, that's right. I hope my contribution gets accepted soon, and I receive feedback 😬. Good luck to you too.

the-coder-o avatar Feb 26 '24 02:02 the-coder-o

Mmmh! I suppose we were on the same page regarding the addition of the discussion highlight badge. 😅 😊 Haha, yes, that's right. I hope my contribution gets accepted soon, and I receive feedback 😬. Good luck to you too.

why copy paste words @the-coder-o :smile:

the1Riddle avatar Feb 26 '24 06:02 the1Riddle

gooooood

the-coder-o avatar Feb 26 '24 09:02 the-coder-o