Make images accessible in the images/help/repository directory (P-Z) (3/4) (#35990)
Co-authored-by: Jules <19994093+jules-p@users.noreply.github.com>
This commit is contained in:
Laura Coursen
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 77 KiB |
BIN
assets/images/help/actions/re-run-selected-job.png
Normal file
BIN
assets/images/help/actions/re-run-selected-job.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 116 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 75 KiB After Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.6 KiB After Width: | Height: | Size: 130 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 77 KiB After Width: | Height: | Size: 182 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 110 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 311 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 128 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1012 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 60 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 73 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.1 KiB After Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 67 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 59 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 140 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 363 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 102 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.4 KiB |
@@ -22,7 +22,7 @@ You decide what information to include in your profile README, so you have full
|
||||
- Contributions you're proud of, and context about those contributions
|
||||
- Guidance for getting help in communities where you're involved
|
||||
|
||||
|
||||
|
||||
|
||||
You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
|
||||
|
||||
@@ -51,17 +51,14 @@ You can send an invitation to collaborate in your repository directly to someone
|
||||
1. Click **Add people**.
|
||||
1. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
|
||||
1. Click **Add NAME to REPOSITORY**.
|
||||
|
||||
{% else %}
|
||||
1. In the left sidebar, click **Collaborators**.
|
||||
1. Under "Collaborators", start typing the collaborator's username.
|
||||
1. Select the collaborator's username from the dropdown menu.
|
||||
|
||||
8. Click **Add collaborator**.
|
||||
|
||||
1. Click **Add collaborator**.
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
|
||||
1. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -36,7 +36,6 @@ While forks of private repositories are deleted when a collaborator is removed,
|
||||
|
||||
{% else %}
|
||||
3. In the left sidebar, click **Collaborators & teams**.
|
||||
|
||||
4. Next to the collaborator you want to remove, click the **X** icon.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -22,12 +22,9 @@ shortTitle: Remove yourself
|
||||
---
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
|
||||
1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-hidden="true" %} Repositories**.
|
||||
{% else %}
|
||||
2. In the left sidebar, click **Repositories**.
|
||||
|
||||
1. In the left sidebar, click **Repositories**.
|
||||
{% endif %}
|
||||
3. Next to the repository you want to leave, click **Leave**.
|
||||
|
||||
4. Read the warning carefully, then click "I understand, leave this repository."
|
||||
|
||||
1. Next to the repository you want to leave, click **Leave**.
|
||||
1. Read the warning carefully, then click **I understand, leave this repository.**
|
||||
|
||||
@@ -117,10 +117,8 @@ When you re-run a specific job in a workflow, a new workflow run will start for
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
1. Next to the job that you want to re-run, click {% octicon "sync" aria-label="The re-run icon" %}.
|
||||
|
||||
|
||||
Alternatively, click on a job to view the log. In the log, click {% octicon "sync" aria-label="The re-run icon" %}.
|
||||
|
||||
|
||||
{% data reusables.actions.enable-debug-logging %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: Add a license to a repo
|
||||
---
|
||||
If you include a detectable license in your repository, people who visit your repository will see it at the top of the repository page. To read the entire license file, click the license name.
|
||||
|
||||
|
||||
|
||||
|
||||
Open source licenses enable others to freely use, change, and distribute the project in your repository. For more information on repository licenses, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
|
||||
|
||||
|
||||
@@ -33,9 +33,9 @@ For more information, see "[AUTOTITLE](/get-started/exploring-projects-on-github
|
||||
|
||||
You can subscribe to a repository to watch it and receive notifications for activity in it. When the owner updates the repository, you will see the changes in your personal dashboard. For more information, see "[AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions)."
|
||||
|
||||
Click **Watch** at the top of a repository to watch it.
|
||||
To watch a repository, at the top of the page, click **Watch**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Joining the conversation
|
||||
|
||||
|
||||
@@ -27,9 +27,9 @@ $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSIT
|
||||
# Clones a repository to your computer
|
||||
```
|
||||
|
||||
You can choose from [several different URLs](/get-started/getting-started-with-git/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available below the repository details:
|
||||
You can choose from [several different URLs](/get-started/getting-started-with-git/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available on the main page of the repository when you click **{% octicon "code" aria-hidden="true" %} Code**.
|
||||
|
||||
|
||||
|
||||
|
||||
When you run `git clone`, the following actions occur:
|
||||
- A new folder called `repo` is made
|
||||
|
||||
@@ -15,11 +15,12 @@ topics:
|
||||
- Pull requests
|
||||
shortTitle: Permanent links to code
|
||||
---
|
||||
|
||||
## Linking to code
|
||||
|
||||
This type of permanent link will render as a code snippet only in the repository it originated in. In other repositories, the permalink code snippet will render as a URL.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -28,15 +29,15 @@ This type of permanent link will render as a code snippet only in the repository
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. Locate the code you'd like to link to:
|
||||
1. Locate the code you'd like to link to:
|
||||
- To link to code from a file, navigate to the file.
|
||||
- To link to code from a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**.
|
||||
{% data reusables.repositories.choose-line-or-range %}
|
||||
4. To the left of the line or range of lines, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. In the drop-down menu, click **Copy permalink**.
|
||||
|
||||
5. Navigate to the conversation where you want to link to the code snippet.
|
||||
6. Paste your permalink into a comment, and click **Comment**.
|
||||
|
||||
1. To the left of the line or range of lines, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the drop-down menu, click **Copy permalink**.
|
||||
|
||||
|
||||
1. Navigate to the conversation where you want to link to the code snippet.
|
||||
1. Paste your permalink into a comment, and click **Comment**.
|
||||
|
||||
## Linking to Markdown
|
||||
|
||||
|
||||
@@ -26,7 +26,8 @@ You can set commit permissions when you first create a pull request from a fork.
|
||||
|
||||
1. On {% data variables.product.product_name %}, navigate to the main page of the upstream repository of your pull request.
|
||||
1. Under the upstream repository name, click {% octicon "git-pull-request" aria-hidden="true" %} **Pull requests**.
|
||||
|
||||
|
||||
|
||||
1. In the list of pull requests, navigate to the pull request that you'd like to allow commits on.
|
||||
{% data reusables.repositories.allow-maintainers-user-forks %}
|
||||
|
||||
|
||||
@@ -32,9 +32,7 @@ Some deleted repositories can be restored within 90 days of deletion. {% ifversi
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
2. Under Danger Zone, click **Delete this repository**.
|
||||
|
||||
3. **Read the warnings**.
|
||||
4. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
|
||||
|
||||
5. Click **I understand the consequences, delete this repository**.
|
||||
1. In the "Danger Zone" section, click **Delete this repository**.
|
||||
1. **Read the warnings**.
|
||||
1. To verify that you're deleting the correct repository, in the text box, type the name of the repository you want to delete.
|
||||
1. Click **I understand the consequences, delete this repository**.
|
||||
|
||||
@@ -42,9 +42,9 @@ If a repository contains more than one README file, then the file shown is chose
|
||||
|
||||
## Auto-generated table of contents for README files
|
||||
|
||||
For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %} menu icon at the top left of the rendered page.
|
||||
For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="Table of Contents" %} menu icon at the top left of the rendered page.
|
||||
|
||||
|
||||
|
||||
|
||||
## Section links in README files and blob pages
|
||||
|
||||
|
||||
@@ -87,17 +87,10 @@ For information about improving repository security, see "[AUTOTITLE](/code-secu
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**.
|
||||
|
||||
4. Select a visibility.
|
||||
{% ifversion fpt or ghec %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
|
||||
6. Click **I understand, change repository visibility**.
|
||||
{% ifversion fpt or ghec %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
1. In the "Danger Zone" section, to the right of to "Change repository visibility", click **Change visibility**.
|
||||
1. Select a visibility.
|
||||
1. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
|
||||
1. Click **I understand, change repository visibility**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -47,14 +47,11 @@ shortTitle: Edit files
|
||||
When you edit a file in another user's repository, we'll automatically [fork the repository](/get-started/quickstart/fork-a-repo) and [open a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) for you.
|
||||
|
||||
1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit.
|
||||
2. Above the file content, click {% octicon "pencil" aria-label="Edit file" %}. At this point, GitHub forks the repository for you.
|
||||
3. In the text box, make any changes you need to the file.
|
||||
1. Above the file content, click {% octicon "pencil" aria-label="Edit file" %}. At this point, {% data variables.product.prodname_dotcom %} forks the repository for you.
|
||||
1. In the text box, make any changes you need to the file.
|
||||
{% data reusables.files.preview_change %}
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose-commit-email %}
|
||||
1. Click **Propose file change**.
|
||||
|
||||
|
||||
|
||||
1. Type a title and description for your pull request.
|
||||
1. Click **Create pull request**.
|
||||
@@ -96,7 +96,8 @@ Rather than losing file context when you enter the blame view, you can now use t
|
||||
|
||||
1. Select a repository, then click a file within that repository to open the new code view.
|
||||
1. To see the revision history of the file, above the file content, click **Blame**. This view gives you a line-by-line revision history, with the code in a file separated by commit. Each commit lists the author, commit description, and commit date.
|
||||
- To see versions of a file before a particular commit, click {% octicon "versions" aria-label="The versions icon" %}. Alternatively, to see more detail about a particular commit, click the commit message.
|
||||
- To see versions of a file before a particular commit, click {% octicon "versions" aria-label="View blame prior to this change" %}. Alternatively, to see more detail about a particular commit, click the commit message.
|
||||
|
||||
|
||||
|
||||
1. To return to the raw code view, above the file content, click **Code**.
|
||||
|
||||
@@ -23,19 +23,14 @@ With the raw view, you can view or copy the raw content of a file without any st
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Click the file that you want to view.
|
||||
2. In the upper-right corner of the file view, click **Raw**.
|
||||
|
||||
3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
|
||||
1. In the upper-right corner of the file view, click **Raw**.
|
||||
|
||||
|
||||
1. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="Copy raw content" %}**.
|
||||
|
||||
## Viewing the line-by-line revision history for a file
|
||||
|
||||
Within the blame view, you can view the line-by-line revision history for an entire file. To view the revision history of a single line within a file, click {% octicon "versions" aria-label="View blame prior to this change" %}. Each time you click {% octicon "versions" aria-label="View blame prior to this change" %}, you'll see the previous revision information for that line, including who committed the change and when.
|
||||
|
||||
|
||||
|
||||
In a file or pull request, you can also view Git blame for a selected line or range of lines by selecting the {% octicon "kebab-horizontal" aria-label="Code line X options" %} dropdown menu, then clicking **View git blame**.
|
||||
|
||||
|
||||
Within the blame view, you can view the line-by-line revision history for an entire file.
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -44,11 +39,12 @@ In a file or pull request, you can also view Git blame for a selected line or ra
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. Click to open the file whose line history you want to view.
|
||||
3. In the upper-right corner of the file view, click **Blame** to open the blame view.
|
||||
1. Click to open the file whose line history you want to view.
|
||||
1. In the upper-right corner of the file view, click **Blame** to open the blame view.
|
||||
|
||||
4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
|
||||
|
||||
1. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="View blame prior to this change" %} until you've found the changes you're interested in viewing.
|
||||
|
||||
|
||||
|
||||
{% ifversion blame-ignore-revs %}
|
||||
|
||||
|
||||
@@ -96,9 +96,7 @@ You can also select the **Revision Slider** option, which lets you use a slider
|
||||
|
||||
### Fixing slow performance
|
||||
|
||||
If you see this icon in the corner of the viewer, then the WebGL technology is not available on your browser:
|
||||
|
||||
|
||||
If you see {% octicon "info" aria-label="the info icon" %} in the corner of the viewer, with the tooltip "WebGL powered hardware support not available," then the WebGL technology is not available on your browser.
|
||||
|
||||
WebGL is necessary to take advantage of your computer's hardware to its fullest. We recommend you try browsers like [Chrome](https://www.google.com/intl/en/chrome/browser/) or [Firefox](https://www.mozilla.org/en-US/firefox/new/), which ship with WebGL enabled.
|
||||
|
||||
@@ -136,9 +134,9 @@ You can embed ASCII STL syntax directly in Markdown. For more information, see "
|
||||
|
||||
## Rendering CSV and TSV data
|
||||
|
||||
GitHub supports rendering tabular data in the form of *.csv* (comma-separated) and .*tsv* (tab-separated) files.
|
||||
{% data variables.product.prodname_dotcom %} supports rendering tabular data in the form of *.csv* (comma-separated) and .*tsv* (tab-separated) files.
|
||||
|
||||
|
||||
|
||||
|
||||
When viewed, any _.csv_ or _.tsv_ file committed to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} automatically renders as an interactive table, complete with headers and row numbering. By default, we'll always assume the first row is your header row.
|
||||
|
||||
@@ -163,9 +161,7 @@ Common errors include:
|
||||
|
||||
## Rendering PDF documents
|
||||
|
||||
GitHub supports rendering of PDF documents.
|
||||
|
||||
|
||||
{% data variables.product.prodname_dotcom %} supports rendering of PDF documents.
|
||||
|
||||
Currently, links within PDFs are ignored.
|
||||
|
||||
@@ -189,11 +185,13 @@ Prose rendering is supported for rendered documents supported by [github/markup]
|
||||
* MediaWiki
|
||||
* Pod
|
||||
|
||||
|
||||
To see the changes made to the document as part of a commit, click {% octicon "file" aria-label="Display the rich diff" %}.
|
||||
|
||||
You can click {% octicon "file" aria-label="The paper icon" %} to see the changes made to the document as part of a commit.
|
||||
|
||||
|
||||
|
||||
This "rich diff" highlights the code that has been added and removed.
|
||||
|
||||
|
||||
|
||||
### Disabling Markdown rendering
|
||||
|
||||
@@ -205,7 +203,7 @@ We provide a tooltip
|
||||
describing changes to attributes that, unlike words, would not otherwise be visible in the rendered document. For example, if a link URL changes from one website to
|
||||
another, we'd show a tooltip like this:
|
||||
|
||||
|
||||
|
||||
|
||||
### Commenting on changes
|
||||
|
||||
@@ -222,8 +220,6 @@ of your rendered prose diff to specific sections.
|
||||
|
||||
Some pull requests involve a large number of changes with large, complex documents. When the changes take too long to analyze, {% data variables.product.product_name %} can't always produce a rendered view of the changes. If this happens, you'll see an error message when you click the rendered button.
|
||||
|
||||
|
||||
|
||||
You can still use the source view to analyze and comment on changes.
|
||||
|
||||
### Viewing HTML elements
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. Click **Propose file change**.
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Under your repository name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**.
|
||||
|
||||
1. Under your repository name, click {% octicon "graph" aria-hidden="true" %} **Insights**.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
You can link directly to a section in a rendered file by hovering over the section heading to expose the link:
|
||||
You can link directly to a section in a rendered file by hovering over the section heading to expose {% octicon "link" aria-label="the link" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,2 +1,3 @@
|
||||
1. Under your repository name, click {% octicon "issue-opened" aria-label="The issues icon" %} **Issues** or {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests**.
|
||||
|
||||
1. Under your repository name, click {% octicon "issue-opened" aria-hidden="true" %} **Issues** or {% octicon "git-pull-request" aria-hidden="true" %} **Pull requests**.
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
2. Under your repository name, click {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**.
|
||||
1. Under your repository name, click {% octicon "issue-opened" aria-hidden="true" %} **Issues**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
1. Under your repository name, click {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests**.
|
||||
{% ifversion fpt or ghec %}
|
||||
{% elsif ghes or ghae %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
1. Under your repository name, click {% octicon "git-pull-request" aria-hidden="true" %} **Pull requests**.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user