Merge pull request github#17305 from github/repo-sync

repo sync

Author: Octomerger

content/README.md

@@ -336,7 +336,11 @@ Just add a hyphen on either the left, right, or both sides to indicate that ther
 
 ## Links and image paths
 
-Local links must start with a product ID (like `/actions` or `/admin`), and image paths must start with `/assets`. The links to Markdown pages undergo some transformations on the server side to match the current page's language and version. The handling for these transformations lives in [`lib/render-content/plugins/rewrite-local-links`](lib/render-content/plugins/rewrite-local-links.js).
+Links to docs in the `docs-internal` repository must start with a product ID (like `/actions` or `/admin`) and contain the entire filepath, but not the file extension. For example, `/actions/creating-actions/about-custom-actions`.
+
+Image paths must start with `/assets` and contain the entire filepath including the file extension. For example, `/assets/images/help/settings/settings-account-delete.png`.
+
+The links to Markdown pages undergo some transformations on the server side to match the current page's language and version. The handling for these transformations lives in [`lib/render-content/plugins/rewrite-local-links`](lib/render-content/plugins/rewrite-local-links.js).
 
 For example, if you include the following link in a content file:
 
@@ -364,6 +368,12 @@ Sometimes you want to link to a Dotcom-only article in Enterprise content and yo
 
 Sometimes the canonical home of content moves outside the docs site. None of the links included in [`lib/redirects/external-sites.json`](/lib/redirects/external-sites.json) get rewritten. See  [`contributing/redirects.md`](/contributing/redirects.md) for more info about this type of redirect.
 
+### Legacy filepaths and redirects for links
+
+Our docs contain links that use legacy filepaths such as `/article/article-name` or `/github/article-name`. Our docs also contain links that refer to articles by past names. Both of these link types function properly because of redirects, but they are bugs.
+
+When you add a link to an article, use the current filepath and article name.
+
 ### Index pages
 
 Index pages are the Table of Contents files for the docs site. Every product, category, and map topic subdirectory has an `index.md` that serves as the landing page. Each `index.md` must contain a `children` frontmatter property with a list of relative links to the child pages of the product, category, or map topic.

contributing/content-style-guide.md

@@ -230,7 +230,11 @@ For plain text, use linebreaks to separate paragraphs in the source (two consecu
 
 ## Links
 
-Introduce links consistently using a standard format that clearly indicates where we’re linking: "For more information, see X [or "Page/article title"] in the X documentation." Do not include quotation marks within a hyperlink.
+Introduce links consistently using a standard format that clearly indicates where we’re linking.
+For links to other articles in the GitHub docs: `For more information, see "[Page or article title]()."`
+For links to another section in the same article: `For more information, see "[Header text]()."`
+For links to external documentation: `For more information, see [Page or article title]() in the X documentation.`
+Do not include quotation marks within a hyperlink.
 
 Links should be meaningful and provide high value to the user’s journey - link out carefully. Move links that are helpful but not necessary to an article’s further reading section. Do not repeat the same link more than once in the same article or under the same H2 header.
 

translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md

@@ -82,7 +82,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
         - run: echo Hello ${{ inputs.who-to-greet }}.
           shell: bash
         - id: random-number-generator
-          run: echo "::set-output name=random-id::$(echo $RANDOM)"
+          run: echo "::set-output name=random-number::$(echo $RANDOM)"
           shell: bash
         - run: echo "${{ github.action_path }}" >> $GITHUB_PATH
           shell: bash          

translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md

@@ -50,9 +50,7 @@ You can configure a {% data variables.product.prodname_actions %} _workflow_ to
 
 ### ワークフロー
 
-A workflow is a configurable automated process that will run one or more jobs.  Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.
-
-You can have multiple workflows in a repository, each of which can perform a different set of steps.  For example, you can have one workflow to build and test pull requests, another workflow to deploy your application every time a release is created, and still another workflow that adds a label every time someone opens a new issue.
+{% data reusables.actions.about-workflows-long %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
 
@@ -86,168 +84,7 @@ You can write your own actions, or you can find actions to use in your workflows
 
 {% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
 
-## サンプルワークフローを作成する
-
-{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory called `.github/workflows`.
-
-コードがプッシュされるたびに一連のコマンドを自動的にトリガーするサンプルワークフローをリポジトリに作成できます。 このワークフローでは、{% data variables.product.prodname_actions %} がプッシュされたコードをチェックアウトし、ソフトウェアの依存関係をインストールして、`bats-v` を実行します。
-
-1. リポジトリに、ワークフローファイルを保存するための `.github/workflows/` ディレクトリを作成します。
-1. `.github/workflows/` ディレクトリに、`learn-github-actions.yml` という名前の新しいファイルを作成し、次のコードを追加します。
-
-   ```yaml
-   name: learn-github-actions
-   on: [push]
-   jobs:
-     check-bats-version:
-       runs-on: ubuntu-latest
-       steps:
-         - uses: {% data reusables.actions.action-checkout %}
-         - uses: {% data reusables.actions.action-setup-node %}
-           with:
-             node-version: '14'
-         - run: npm install -g bats
-         - run: bats -v
-   ```
-1. これらの変更をコミットして、{% data variables.product.prodname_dotcom %} リポジトリにプッシュします。
-
-これで、新しい {% data variables.product.prodname_actions %} ワークフローファイルがリポジトリにインストールされ、別のユーザがリポジトリに変更をプッシュするたびに自動的に実行されます。 For details about a workflow's execution history, see "[Viewing the workflow's activity](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-workflows-activity)."
-
-## ワークフローファイルを理解する
-
-YAML 構文を使用してワークフローファイルを作成する方法を理解しやすくするために、このセクションでは、導入例の各行について説明します。
-
-<table>
-<tr>
-<td>
-
-  ```yaml
-  name: learn-github-actions
-  ```
-</td>
-<td>
-  <em>オプション</em> - {% data variables.product.prodname_dotcom %} リポジトリの [Actions] タブに表示されるワークフローの名前。
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-  on: [push]
-  ```
-</td>
-<td>
-Specifies the trigger for this workflow. This example uses the <code>push</code> event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request.  This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see <a href="https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-  jobs:
-  ```
-</td>
-<td>
- Groups together all the jobs that run in the <code>learn-github-actions</code> workflow.
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-  check-bats-version:
-  ```
-</td>
-<td>
-Defines a job named <code>check-bats-version</code>. The child keys will define properties of the job.
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-    runs-on: ubuntu-latest
-  ```
-</td>
-<td>
-  Configures the job to run on the latest version of an Ubuntu Linux runner. これは、ジョブが GitHub によってホストされている新しい仮想マシンで実行されるということです。 他のランナーを使用した構文例については、「<a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">{% data variables.product.prodname_actions %} のワークフロー構文</a>」を参照してください。
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-    steps:
-  ```
-</td>
-<td>
-  <code>check-bats-version</code> ジョブで実行されるすべてのステップをグループ化します。 Each item nested under this section is a separate action or shell script.
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-      - uses: {% data reusables.actions.action-checkout %}
-  ```
-</td>
-<td>
-The <code>uses</code> keyword specifies that this step will run <code>v3</code> of the <code>actions/checkout</code> action.  This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will run against the repository's code.
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-      - uses: {% data reusables.actions.action-setup-node %}
-        with:
-          node-version: '14'
-  ```
-</td>
-<td>
-  This step uses the <code>{% data reusables.actions.action-setup-node %}</code> action to install the specified version of the Node.js (this example uses v14). This puts both the <code>node</code> and <code>npm</code> commands in your <code>PATH</code>.
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-      - run: npm install -g bats
-  ```
-</td>
-<td>
-  <code>run</code> キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、<code>npm</code> を使用して <code>bats</code> ソフトウェアテストパッケージをインストールしています。
-</td>
-</tr>
-<tr>
-<td>
-
-  ```yaml
-      - run: bats -v
-  ```
-</td>
-<td>
-  最後に、ソフトウェアバージョンを出力するパラメータを指定して <code>bats</code> コマンドを実行します。
-</td>
-</tr>
-</table>
-
-### ワークフローファイルの視覚化
-
-この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
-
-![ワークフローの概要](/assets/images/help/images/overview-actions-event.png)
-
-## Viewing the workflow's activity
-
-Once your workflow has started running, you can see a visualization graph of the run's progress and view each step's activity on {% data variables.product.prodname_dotcom %}.
-
-{% data reusables.repositories.navigate-to-repo %}
-1. リポジトリ名の下で**Actions（アクション）**をクリックしてください。 ![リポジトリに移動](/assets/images/help/images/learn-github-actions-repository.png)
-1. 左サイドバーで、表示するワークフローをクリックします。 ![ワークフロー結果のスクリーンショット](/assets/images/help/images/learn-github-actions-workflow.png)
-1. [Workflow runs] で、表示する実行の名前をクリックします。 ![ワークフロー実行のスクリーンショット](/assets/images/help/images/learn-github-actions-run.png)
-1. [**Jobs**] または視覚化グラフで、表示するジョブをクリックします。 ![ジョブを選択](/assets/images/help/images/overview-actions-result-navigate.png)
-1. 各ステップの結果を表示します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated-2.png)
+{% data reusables.actions.workflow-basic-example-and-explanation %}
 
 ## 次のステップ
 
@@ -263,7 +100,8 @@ To understand how billing works for {% data variables.product.prodname_actions %
 
 {% data reusables.actions.contacting-support %}
 
+{% ifversion ghec or ghes or ghae %}
 ## 参考リンク
 
-{% ifversion ghec or ghes or ghae %}
-- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"{% endif %}
+- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"
+{% endif %}