-
Notifications
You must be signed in to change notification settings - Fork 65.4k
Update customizing-your-organizations-profile.md #13377
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
Conversation
Added some image slides showing how to create organization's profile
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
|
|
@kum9748ar |
lecoursen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kum9748ar! After you incorporate my feedback, we'll review this PR again.
|  | ||
|
|
||
| 2. Optionally, add a description of your organization's repository. For example, "My organization's repository." | ||
|
|
||
|  | ||
|
|
||
| 3. Select **Public** | ||
|
|
||
|  | ||
|
|
||
| 4. Select any one form **Initialize this repository**. | ||
|
|
||
|  | ||
|
|
||
| 5. Click **Create repository.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Steps 2-5 are all part of creating a .github repository, which is step 1. Instead of adding these steps, let's add a link to the existing procedure at the end of the existing step 1:
|
|
||
|  | ||
|
|
||
| 7. The generated README file is pre-populated with a template to give you some inspiration for your organization's profile README. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each procedural step needs to be an imperative (command). We can add context like this after the imperative.
| 7. The generated README file is pre-populated with a template to give you some inspiration for your organization's profile README. | |
| 7. Edit the generated README file, which is pre-populated with a template to give you some inspiration for your organization's profile README. |
|
|
||
|  | ||
|
|
||
| For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](http://www.emoji-cheat-sheet.com/)." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove this line. It might be interesting to some folks, but it makes the procedure longer and therefore increases the cognitive load of reading the article, without being useful enough to justify that. We should only document what users need to know to be successful in their task.
|
@kum9748ar Checking in to see if you are still able to work on this PR 💖. Thanks so much for your time in contributing to the GitHub docs ✨ . |
|
A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days. |
Added some image slides showing how to create organization's profile
Why:
Closes #13376
What's being changed:
Check off the following:
Writer impact (This section is for GitHub staff members only):