-
-
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
Add @mfrw as a collaborator #2306
Comments
@sbrl was it intentional that you linked to the PRs in some cases and to the issues in others? I think it would be more consistent to link to the PRs in all cases. |
Thank you folks for the opportunity. |
@mfrw repeating what I said on Gitter, for the record:
|
Nope, not intentional @waldyrious :P - I've corrected that. I've also actually invited you to be a collaborator now @mfrw, so clicking this link should take you to the invite if you don't receive an email. |
Should we close this now ? |
Yep. Welcome aboard ! |
Btw, looking at the list of repo collaborators, I suppose @pxgamer should have been removed from there when he was added to the org, right? If so, that step should be documented here. |
Hi, @mfrw! You seem to be enjoying contributing to the tldr-pages project. You now have had five distinct pull requests merged (#2297, #2294, #2288, #1651, #1532), which qualifies you to become a collaborator in this repository, as explained in our governance guidelines.
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: