-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add collaborator: @patricedenis #5919
Labels
community
Issues/PRs dealing with role changes and community organization.
Comments
marchersimon
added
the
community
Issues/PRs dealing with role changes and community organization.
label
May 9, 2021
All Right ! 🎆 |
patricedenis
added a commit
to patricedenis/tldr
that referenced
this issue
May 10, 2021
This was referenced May 10, 2021
@patricedenis - @navarroaxel sent an invite. Please accept it! 😍 |
Feel free to merge the PR yourself once you've accepted ;) |
Welcome! |
Thanks ! |
patricedenis
added a commit
that referenced
this issue
May 10, 2021
Welcome! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, @patricedenis ! You seem to be enjoying contributing to the tldr-pages project.
You now have had 15 distinct pull requests merged (#5496, #5497, #5498, #5494, #5495, #5504, #5501, #5503, #5505, #5539, #5699, #5697, #5696, #5738, #5710)!
That qualifies you to become a collaborator in this repository, as explained in our community roles documentation.
As a collaborator, you will have commit access to the repository.
That means you can merge pull requests, label and close issues, and perform various other maintenance tasks that are needed here and there.
Of course, all of this is voluntary — you're welcome to contribute to the project in whatever ways suit your liking.
If you do decide to start performing maintenance tasks, though, we only ask you to get familiar with the maintainer's guide.
So, what do you say? Can we add you as a collaborator?
Either way, thanks for all your work so far!
The text was updated successfully, but these errors were encountered: