You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
36
36
37
37
{% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
38
38
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.
40
40
41
41
```shell
42
42
$ git commit -m "Refactor usability tests.
@@ -45,7 +45,7 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
45
45
```
46
46
47
47
> [!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.
49
49
50
50
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.
51
51
@@ -54,9 +54,8 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
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).
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.
2
2
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
+
```
6
14
7
15
You'll use this variable with the `--target-api-url` option in commands you run with the {% data variables.product.prodname_cli %}.
0 commit comments