jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Update spacing from md037 (#38574)

Browse Source
This commit is contained in:
Grace Park
2023-06-27 09:39:59 -07:00
committed by GitHub
parent 48433d695f
commit dbff98cd20
4 changed files with 10 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/actions/using-workflows/reusing-workflows.md
View File

@@ -86,7 +86,7 @@ Called workflows that are owned by the same user or organization{% ifversion ghe
- Reusable workflows can't call other reusable workflows.
- You can call a maximum of 20 reusable workflows from a single workflow file.
{% endif %}
{% ifversion private-actions %}{% else %}*Reusable workflows stored within a private repository can only be used by workflows within the same repository.{% endif %}
{% ifversion private-actions %}{% else %}- Reusable workflows stored within a private repository can only be used by workflows within the same repository.{% endif %}
{% ifversion actions-reusable-workflow-matrix %}{% else %}* The `strategy` property is not supported in any job that calls a reusable workflow.{% endif %}
- 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)."
- 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).

4
content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
View File

@@ -26,8 +26,8 @@ shortTitle: Existing GPG keys
{% data reusables.command_line.open_the_multi_os_terminal %}
{% data reusables.gpg.list-keys-with-note %}
1. Check the command output to see if you have a GPG key pair.
*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).
* 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`:
- 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).
- 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`:
```shell
$ gpg --armor --export 3AA5C34371567BD2

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

@@ -37,14 +37,12 @@ shortTitle: Export from GHES
{% data reusables.enterprise_installation.ssh-into-instance %}
1. To prepare a repository for export, use the `ghe-migrator add` command with the repository's URL:
*If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed.
- If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed.
```shell
$ ghe-migrator add https://HOSTNAME/USERNAME/REPO-NAME --lock
```
* You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %}
* 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.
- You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %}
- 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.
```shell
$ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URL.txt

8
content/migrations/using-ghe-migrator/exporting-migration-data-from-githubcom.md
View File

@@ -72,10 +72,10 @@ The Migrations API is currently in a preview period, which means that the endpoi
```
A migration can be in one of the following states:
*`pending`, which means the migration hasn't started yet.
* `exporting`, which means the migration is in progress.
*`exported`, which means the migration finished successfully.
* `failed`, which means the migration failed.
- `pending`, which means the migration hasn't started yet.
- `exporting`, which means the migration is in progress.
- `exported`, which means the migration finished successfully.
- `failed`, which means the migration failed.
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:
- Your access token for authentication.