Skip to content

Commit f7d2dfd

Browse files
authored
Merge pull request #54838 from github/repo-sync
Repo sync
2 parents 1f20548 + db0cf5d commit f7d2dfd

File tree

3 files changed

+17
-9
lines changed

3 files changed

+17
-9
lines changed

content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
3636

3737
{% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
3838

39-
1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines.
39+
1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add an empty line.
4040

4141
```shell
4242
$ git commit -m "Refactor usability tests.
@@ -45,7 +45,7 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
4545
```
4646
4747
> [!TIP]
48-
> If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
48+
> If you're using a text editor on the command line to type your commit message, ensure there is a blank line (two consecutive newlines) between the end of your commit description and the `Co-authored-by:` commit trailer.
4949
5050
1. On the next line of the commit message, type `Co-authored-by: name <[email protected]>` with specific information for each co-author. After the co-author information, add a closing quotation mark.
5151
@@ -54,9 +54,8 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
5454
```shell
5555
$ git commit -m "Refactor usability tests.
5656
>
57-
>
58-
Co-authored-by: NAME <[email protected]>
59-
Co-authored-by: ANOTHER-NAME <[email protected]>"
57+
> Co-authored-by: NAME <[email protected]>
58+
> Co-authored-by: ANOTHER-NAME <[email protected]>"
6059
```
6160
6261
The new commit and message will appear on {% data variables.location.product_location %} the next time you push. For more information, see [AUTOTITLE](/get-started/using-git/pushing-commits-to-a-remote-repository).
Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,15 @@
1-
1. If you're migrating to {% data variables.enterprise.data_residency %}, for convenience, set an environment variable for the **base API URL** for your enterprise. For example:
1+
1. If you're migrating to {% data variables.enterprise.data_residency %}, for convenience, set an environment variable for the **base API URL** for your enterprise.
22

3-
```shell copy
4-
export TARGET_API_URL="https://api.{% data variables.enterprise.data_residency_example_domain %}"
5-
```
3+
* If you're using Terminal, use the `export` command.
4+
5+
```shell copy
6+
export TARGET_API_URL="https://api.{% data variables.enterprise.data_residency_example_domain %}"
7+
```
8+
9+
* If you're using PowerShell, use the `$env` command.
10+
11+
```shell copy
12+
$env:TARGET_API_URL="https://api.{% data variables.enterprise.data_residency_example_domain %}"
13+
```
614
715
You'll use this variable with the `--target-api-url` option in commands you run with the {% data variables.product.prodname_cli %}.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
11
1. Click **New ruleset**.
22
1. Click **New branch ruleset**.
33
1. Under "Ruleset name," type a name for the ruleset.
4+
1. To activate the ruleset, under "Enforcement Status", select **Active**.

0 commit comments

Comments
 (0)