-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
AnimiVulpis: add collaborator #2556
Comments
I totally agree adding him! I love his contributions, especially the |
Hmm, reading the opening message above, I think we should end the template with an actionable note. I would suggest such a note to ask them to (1) confirm their agreement that the invitation can be sent, and (2) close the issue once they accept it (thus confirming that the new permissions are in place). |
I think that sounds pretty good @waldyrious 👍 |
Yep that's a good idea. |
Cool, thanks all for the feedback. I've added a note to self to contribute that change soon-ish. |
Now that I accepted to become a collaborator, should I close this issue myself? And thanks a lot 😄 |
According to this -
Yes. |
No problem! and yep, go ahead @AnimiVulpis :D |
Hi, @AnimiVulpis! You seem to be enjoying contributing to the tldr-pages project. You now have had five distinct pull requests merged (#2544, #2542, #2541, #2540, #2539, #1591, #1590, #1589), which qualifies you to become a collaborator in this repository, as explained in our community roles documentation.
As a collaborator, you will have commit access and can therefore merge pull requests from others, 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.
Thanks for all your work so far!
The text was updated successfully, but these errors were encountered: