Recognizing Repositories’ Role Models ⭐ [Repositories Check-in]

[queenofcorgis]

This month we’re doing things a bit differently in this category. Our members are what make this space so great and I want to dedicate some time to share who has made our category so great and how you can follow their footsteps.

Wall of Fame 🤩

• @pedrolemos4: Helped a user enable Code Scanning in their Repository Settings by sharing documentation in their reply. They didn’t need to recreate the wheel or tell the member where to search, but by directly linking them to our Docs they ensured the OP and future askers of this questions had GitHub’s trusted steps to get this enabled.
• @MostlyKIGuess: Wrote a stellar response for duplicating a repository through GitHub’s interface! Their response contained two different options to answer the question which showcased their expertise as a developer and allowed the OP and other users to use the option that worked best for them 💪. And both options were great! They included clear steps, call outs to where buttons may be located, and the Git commands needed and clearly labeled. This answer is so well-written as it is helpful to anyone regardless of their coding background. Well done!
• @electrofelix: Shared amazing feedback on our Push rule private discussion. It was detailed and specific - they shared exactly what they were trying to achieve, what they were encountering, included workarounds they considered, and clearly articulated what their use case was. Bonus: They were responsive to our Product Manager who had follow up questions as well. Thank you for helping us improve @electrofelix!

Being a great community citizen 🌏

How you can help others, further develop your own skills, and even get recognized yourself!

• Have the Heart of a Teacher 🧑‍🏫: Kindness, compassion, inspiration, and the joy of learning
  • We may not have all the answers, but we have a positive mindset and a desire to build and help others.
  • I appreciate how upbeat @CopperEagle was in their comment and the great screenshots they used to explain the answer.
• Be Authentic 💟: Verify what you are sharing and take personal responsibility for what you’re posting
  • Read and revise the content before you post it, do not just post AI-generated content verbatim to inflate your reputation or give a false impression of product expertise.
  • Not only do they remind other users to be authentic, but @markolalovic also shared notes and another Discussion in their response for a robust response.
• Don’t Assume 😀: The GitHub Community is made up of users all over the world and of varying abilities and lived experiences
  • Approach other users with curiosity and an open mind, we can all learn from one another!
  • This comment from @davevad93 was a great example of this as he included background information and didn’t assume any prior knowledge making this response useful for anyone! Also kudos to linking to further information as well 👏.
• Ask Questions ❓: What have they tried already? Which version are they using? Do they have any screenshots?
  • Asking Questions encourages folks to add more information which makes it more likely they’ll get a response.
  • @gurjeetsinghvirdee did just that when trying to assist here.
• Use Links 🔗: Documentation, YouTube, a helpful project hosted on GitHub that may be a workaround or answer their questions, be sure to share any context or additional knowledge too!
  • We have so much information at our disposal, by sharing what we’ve found to work circulates quality content and increases all our knowledge.
  • @spenserblack included two links in their reply. One link was explaining what submodules are and they included their own summary. Then what really took this to the next level, was they also used a link to showcase an example of what a submodules file will look like. Bravo!

A huge thank you to @spenserblack, @gurjeetsinghvirdee, @davevad93, @markolalovic, @CopperEagle, @electrofelix, @MostlyKIGuess, and @pedrolemos4 for modeling amazing community behavior 🙇.

Don’t forget, for community members who post questions, marking responses that solves your question as the answer goes a long way. When you mark a comment in the Discussion as an answer, GitHub will highlight the comment to help other community members quickly find the answer as well.

Remember to thank these and other community members that take the time to comment and help troubleshoot these problems. An acknowledgement of a job well done can have an incredible effect and make someone’s day. ☀️ We’re here to learn, discover and connect so try and mark a comment as an answer if suitable, give a thank you and select a reaction as a way to show your appreciation!

Celebrate the above users by giving them some love below!

[MostlyKIGuess]

Lol idk how I got selected, but thank you :3
I am just giving it back .

[queenofcorgis]

@MostlyKIGuess you got selected by doing great work in the community - thank you!

[davevad93]

Thank you @queenofcorgis , I'm so glad to be part of this community!

[queenofcorgis]

@davevad93 Thank you and we are so glad to have you 💟

[CopperEagle]

Thank you very much @queenofcorgis ❤️

(Currently studying for exams so I saw the mention a bit late ;)

[queenofcorgis]

@CopperEagle hope your exams went well!

[CopperEagle]

@queenofcorgis I can't tell yet, I have the exams at the end of summer :) In any case, thanks for your mention ❤️

[queenofcorgis]

@CopperEagle in that case best of luck!