Skip to content

Commit 5bf8c23

Browse files
docs-botdocs-bot
authored
Merge pull request github#26285 from github/repo-sync
Repo sync
2 parents bffd77c + dbff98c commit 5bf8c23

File tree

36 files changed

+10
-564500
lines changed

36 files changed

+10
-564500
lines changed

‎content/actions/using-workflows/reusing-workflows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Called workflows that are owned by the same user or organization{% ifversion ghe
8686
- Reusable workflows can't call other reusable workflows.
8787
- You can call a maximum of 20 reusable workflows from a single workflow file.
8888
{% endif %}
89-
{% ifversion private-actions %}{% else %}*Reusable workflows stored within a private repository can only be used by workflows within the same repository.{% endif %}
89+
{% ifversion private-actions %}{% else %}- Reusable workflows stored within a private repository can only be used by workflows within the same repository.{% endif %}
9090
{% ifversion actions-reusable-workflow-matrix %}{% else %}* The `strategy` property is not supported in any job that calls a reusable workflow.{% endif %}
9191
- Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information, see "[AUTOTITLE](/actions/learn-github-actions/variables)" and "[AUTOTITLE](/actions/learn-github-actions/contexts#env-context)."
9292
- Similarly, environment variables set in the `env` context, defined in the called workflow, are not accessible in the `env` context of the caller workflow. Instead, you must use outputs of the reusable workflow. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow).

‎content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ shortTitle: Existing GPG keys
2626
{% data reusables.command_line.open_the_multi_os_terminal %}
2727
{% data reusables.gpg.list-keys-with-note %}
2828
1. Check the command output to see if you have a GPG key pair.
29-
*If there are no GPG key pairs or you don't want to use any that are available for signing commits and tags, then [generate a new GPG key](/authentication/managing-commit-signature-verification/generating-a-new-gpg-key).
30-
* If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`:
29+
- If there are no GPG key pairs or you don't want to use any that are available for signing commits and tags, then [generate a new GPG key](/authentication/managing-commit-signature-verification/generating-a-new-gpg-key).
30+
- If there's an existing GPG key pair and you want to use it to sign commits and tags, you can display the public key using the following command, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`:
3131

3232
```shell
3333
$ gpg --armor --export 3AA5C34371567BD2

‎content/migrations/using-ghe-migrator/exporting-migration-data-from-github-enterprise-server.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -37,14 +37,12 @@ shortTitle: Export from GHES
3737

3838
{% data reusables.enterprise_installation.ssh-into-instance %}
3939
1. To prepare a repository for export, use the `ghe-migrator add` command with the repository's URL:
40-
*If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed.
41-
40+
- If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed.
4241
```shell
4342
$ ghe-migrator add https://HOSTNAME/USERNAME/REPO-NAME --lock
4443
```
45-
46-
* You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %}
47-
* To prepare multiple repositories at once for export, create a text file listing each repository URL on a separate line, and run the `ghe-migrator add` command with the `-i` flag and the path to your text file.
44+
- You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %}
45+
- To prepare multiple repositories at once for export, create a text file listing each repository URL on a separate line, and run the `ghe-migrator add` command with the `-i` flag and the path to your text file.
4846

4947
```shell
5048
$ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URL.txt

‎content/migrations/using-ghe-migrator/exporting-migration-data-from-githubcom.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -72,10 +72,10 @@ The Migrations API is currently in a preview period, which means that the endpoi
7272
```
7373

7474
A migration can be in one of the following states:
75-
*`pending`, which means the migration hasn't started yet.
76-
* `exporting`, which means the migration is in progress.
77-
*`exported`, which means the migration finished successfully.
78-
* `failed`, which means the migration failed.
75+
- `pending`, which means the migration hasn't started yet.
76+
- `exporting`, which means the migration is in progress.
77+
- `exported`, which means the migration finished successfully.
78+
- `failed`, which means the migration failed.
7979
8080
1. After your migration has exported, download the migration archive by sending a `GET` request to [the migration download endpoint](/free-pro-team@latest/rest/migrations#download-an-organization-migration-archive). You'll need:
8181
- Your access token for authentication.

0 commit comments

Comments
 (0)