1
0
mirror of synced 2026-01-06 15:01:04 -05:00

Merge branch 'main' into patch-1

This commit is contained in:
Martin Lopes
2021-04-07 15:11:23 +10:00
committed by GitHub
6 changed files with 32 additions and 12 deletions

View File

@@ -114,7 +114,7 @@ updates:
interval: "daily"
# Overwrite any ignores created using `@dependabot ignore` commands
ignore:
# Ignore updates to packages that start 'aws'
# Ignore updates to packages that start with 'aws'
# Wildcards match zero or more arbitrary characters
- dependency-name: "aws*"
# Ignore some updates to the 'express' package

View File

@@ -183,6 +183,20 @@ This event returns an empty `payload` object.
{% data reusables.webhooks.pull_request_event_api_properties %}
{% data reusables.webhooks.pull_request_properties %}
### PullRequestReviewEvent
{% data reusables.webhooks.pull_request_review_short_desc %}
{% data reusables.webhooks.events_api_payload %}
#### Event `payload` object
Key | Type | Description
----|------|-------------
`action` | `string` | The action that was performed. Can be `created`.
`pull_request` | `object` | The pull request the review pertains to.
`review` | `object` | The review that was affected.
### PullRequestReviewCommentEvent
{% data reusables.webhooks.pull_request_review_comment_short_desc %}
@@ -200,6 +214,8 @@ This event returns an empty `payload` object.
{% data reusables.webhooks.events_api_payload %}
#### Event `payload` object
Key | Type | Description
----|------|-------------
`push_id` | `integer` | Unique identifier for the push.

View File

@@ -4,7 +4,7 @@ intro: You can change the name of a branch in a repository.
permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch.
versions:
free-pro-team: '*'
enterprise-server: '>=3.1'
enterprise-server: '>=3.2'
topics:
- repositories
---
@@ -13,7 +13,9 @@ topics:
You can rename a branch in a repository on {% data variables.product.product_location %}. For more information about branches, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches)."
If you rename a branch, {% data variables.product.prodname_dotcom %} will automatically redirect links on {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location_enterprise %}{% endif %} that contain the old branch name to the equivalent link on the renamed branch. {% data variables.product.prodname_dotcom %} will also update branch protection policies, as well as the base branch for open pull requests and draft releases.
When you rename a branch on {% data variables.product.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments.
Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
### Renaming a branch

View File

@@ -18,7 +18,7 @@ topics:
{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to
determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch.
Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist#troubleshooting) for help.
Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help.
### Markup languages

View File

@@ -23,13 +23,13 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of
```
3. Mirror-push to the new repository.
```shell
$ cd <em>old-repository</em>.git
$ cd <em>old-repository</em>
$ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
```
4. Remove the temporary local repository you created earlier.
```shell
$ cd ..
$ rm -rf <em>old-repository</em>.git
$ rm -rf <em>old-repository</em>
```
### Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects
@@ -41,7 +41,7 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of
```
3. Navigate to the repository you just cloned.
```shell
$ cd <em>old-repository</em>.git
$ cd <em>old-repository</em>
```
4. Pull in the repository's {% data variables.large_files.product_name_long %} objects.
```shell
@@ -58,7 +58,7 @@ Before you can duplicate a repository and push to your new copy, or _mirror_, of
7. Remove the temporary local repository you created earlier.
```shell
$ cd ..
$ rm -rf <em>old-repository</em>.git
$ rm -rf <em>old-repository</em>
```
### Mirroring a repository in another location
@@ -72,7 +72,7 @@ If you want to mirror a repository in another location, including getting update
```
3. Set the push location to your mirror.
```shell
$ cd <em>repository-to-mirror</em>.git
$ cd <em>repository-to-mirror</em>
$ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>mirrored</em>
```

View File

@@ -33,7 +33,7 @@ If your site administrator has disabled private mode, you can also use anonymous
You'll receive a notification when:
- You are the author of a gist.
- Someone mentions you in a gist.
- You subscribe to a gist, by clicking **Subscribe** at the top any gist.
- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
@@ -55,13 +55,15 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists,
### Creating a gist
You can also drag and drop a text file from your desktop directly into the gist editor.
Follow the steps below to create a gist.
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
{% note %}
You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation.
Alternatively, you can drag and drop a text file from your desktop directly into the editor.
{% endnote %}
{% endif %}
@@ -70,7 +72,7 @@ You can also create a gist using the {% data variables.product.prodname_cli %}.
3. Type an optional description and name for your gist.
![Gist name description](/assets/images/help/gist/gist_name_description.png)
4. Type the text of your gist into the gist text box.
4. Type the text of your gist into the gist text box.
![Gist text box](/assets/images/help/gist/gist_text_box.png)
5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**.