[Accessibility] Update remaining images in repository A–C (#36656)
This commit is contained in:
Annelisa Stephan
@@ -96,7 +96,6 @@ The "Used by" section represents a single package from the repository. If you ha
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
4. Under "Code security and analysis", click the drop-down menu in the "Used by counter" section and choose a package.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -29,7 +29,12 @@ If a comment is off-topic, outdated, or resolved, you may want to hide a comment
|
||||
|
||||
|
||||
|
||||
3. Using the "Choose a reason" drop-down menu, click a reason to hide the comment. Then click, **Hide comment**.
|
||||
3. Using the "Choose a reason" dropdown menu, choose a reason to hide the comment. Then select **Hide comment**.
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Unhiding a comment
|
||||
|
||||
|
||||
@@ -30,13 +30,11 @@ You can create a default code of conduct for your organization or personal accou
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.files.add-file %}
|
||||
3. In the file name field, type *CODE_OF_CONDUCT.md*.
|
||||
4. Click **Choose a code of conduct template**.
|
||||
|
||||
4. Select **Choose a code of conduct template**.
|
||||
|
||||
5. On the left side of the page, select a code of conduct to preview and add to your project.
|
||||
|
||||
6. On the right side of the page, complete the fields to populate the selected code of conduct with the appropriate information.
|
||||
7. Click **Review and submit**.
|
||||
|
||||
8. Review the contents of the code of conduct that's in the text area.
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose_commit_branch %}
|
||||
|
||||
@@ -47,7 +47,7 @@ Open source licenses enable others to freely use, change, and distribute the pro
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose-commit-email %}
|
||||
7. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is `main`, you should choose to create a new branch for your commit and then create a pull request. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)".
|
||||
|
||||
|
||||
1. Click **Commit new file**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -47,11 +47,10 @@ You cannot create a default license file. License files must be added to individ
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
1. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
|
||||
|
||||
|
||||
1. In the "Repository name" field, type **.github**.
|
||||
1. Optionally, in the "Description" field, type a description.
|
||||
1. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
|
||||
|
||||
2. Make sure the repository status is set to **Public**. A repository for default files cannot be private.
|
||||
{% data reusables.repositories.initialize-with-readme %}
|
||||
{% data reusables.repositories.create-repo %}
|
||||
1. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
|
||||
|
||||
@@ -34,8 +34,7 @@ topics:
|
||||
{% data reusables.repositories.create_new %}
|
||||
1. Optionally, to create a repository with the directory structure and files of an existing repository, select the **Choose a template** dropdown menu and click a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)."
|
||||
1. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
|
||||
1. In the Owner dropdown, select the account you wish to create the repository on.
|
||||
|
||||
{% data reusables.repositories.owner-drop-down %}
|
||||
{% data reusables.repositories.repo-name %}
|
||||
{% data reusables.repositories.choose-repo-visibility %}
|
||||
1. If you're not using a template, there are a number of optional items you can pre-populate your repository with. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[AUTOTITLE](/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line)," "[AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts)."
|
||||
|
||||
Reference in New Issue
Block a user