-
Notifications
You must be signed in to change notification settings - Fork 59.6k
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
Include the issue and pull request sidebar as a method for assigning users #3579
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 has been minimized.
This comment has been minimized.
@labrose Great catch! I think the procedural in this article could be completely updated to match the flow in the gif. Anyone is welcome to open a pull request to make this change! You'll need to update all of the steps and take new screenshots (without any of your personally identifying information). |
Hi, I would like to take up this issue? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@shades-7 - thanks for your interest but it looks as if there's now an open PR that addresses this issue. Maybe there's another issue that you might be interested in working on: https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22? |
What article on docs.github.com is affected?
https://docs.github.com/en/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users
What part(s) of the article would you like to see updated?
Today the assigning article relies heavily on using the list of issues, but does not mention that users can also assign individual issues to users via the sidebar assignees control.
It would be great to highlight the use case of assigning to an individual, including the quick "assign yourself" action in our documentation.
Additional information
The experience I'm referencing:
The text was updated successfully, but these errors were encountered: