-
Notifications
You must be signed in to change notification settings - Fork 61.9k
Clarify reporting abuse in comments when the user is not a contributor. #20202
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
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
This comment was marked as outdated.
This comment was marked as outdated.
@avalonv Thanks for opening an issue and PR! ✨ |
Hi @avalonv 👋 thank you for raising this issue. I think the pertinent information already exists in the article at line 14. What I would suggest we do is to move the paragraph at line 14 into a permissions statement in the front matter, which will give it more prominence. You can read more about that here: https://github.com/github/docs/blob/main/contributing/content-model.md#permissions-statements You (or anyone else) are welcome to make that change in a new PR, and we will be happy to review it. Thank you again for taking the time to contribute to our docs. ✨ |
Uh oh!
There was an error while loading. Please reload this page.
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam
What changes are you suggesting?
The current doc states only collaborators may report comments on issues and PRs, which gives the impression non-collaborators cannot report specific instances of spam or harassment if they're not contributors. I think a clarification that you still can report a comment through the report user form might be useful for people that were confused about this implementation, such as myself.
Additional information
[maintainer edit]
Content plan here
The text was updated successfully, but these errors were encountered: