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
* Add crowdin translations
* Run script/i18n/homogenize-frontmatter.js
* Run script/i18n/lint-translation-files.js --check rendering
* run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja
* run script/i18n/reset-known-broken-translation-files.js
* Check in ja CSV report
Copy file name to clipboardExpand all lines: translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
+5-167Lines changed: 5 additions & 167 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,9 +50,7 @@ You can configure a {% data variables.product.prodname_actions %} _workflow_ to
50
50
51
51
### ワークフロー
52
52
53
-
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.
54
-
55
-
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.
53
+
{% data reusables.actions.about-workflows-long %}
56
54
57
55
{% 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 %}
58
56
@@ -86,168 +84,7 @@ You can write your own actions, or you can find actions to use in your workflows
86
84
87
85
{% 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)."
88
86
89
-
## サンプルワークフローを作成する
90
-
91
-
{% 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`.
92
-
93
-
コードがプッシュされるたびに一連のコマンドを自動的にトリガーするサンプルワークフローをリポジトリに作成できます。 このワークフローでは、{% data variables.product.prodname_actions %} がプッシュされたコードをチェックアウトし、ソフトウェアの依存関係をインストールして、`bats-v` を実行します。
- uses: {% data reusables.actions.action-checkout %}
106
-
- uses: {% data reusables.actions.action-setup-node %}
107
-
with:
108
-
node-version: '14'
109
-
- run: npm install -g bats
110
-
- run: bats -v
111
-
```
112
-
1. これらの変更をコミットして、{% data variables.product.prodname_dotcom %} リポジトリにプッシュします。
113
-
114
-
これで、新しい {% 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)."
<em>オプション</em> - {% data variables.product.prodname_dotcom %} リポジトリの [Actions] タブに表示されるワークフローの名前。
130
-
</td>
131
-
</tr>
132
-
<tr>
133
-
<td>
134
-
135
-
```yaml
136
-
on: [push]
137
-
```
138
-
</td>
139
-
<td>
140
-
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>
141
-
</td>
142
-
</tr>
143
-
<tr>
144
-
<td>
145
-
146
-
```yaml
147
-
jobs:
148
-
```
149
-
</td>
150
-
<td>
151
-
Groups together all the jobs that run in the <code>learn-github-actions</code> workflow.
152
-
</td>
153
-
</tr>
154
-
<tr>
155
-
<td>
156
-
157
-
```yaml
158
-
check-bats-version:
159
-
```
160
-
</td>
161
-
<td>
162
-
Defines a job named <code>check-bats-version</code>. The child keys will define properties of the job.
163
-
</td>
164
-
</tr>
165
-
<tr>
166
-
<td>
167
-
168
-
```yaml
169
-
runs-on: ubuntu-latest
170
-
```
171
-
</td>
172
-
<td>
173
-
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>」を参照してください。
174
-
</td>
175
-
</tr>
176
-
<tr>
177
-
<td>
178
-
179
-
```yaml
180
-
steps:
181
-
```
182
-
</td>
183
-
<td>
184
-
<code>check-bats-version</code> ジョブで実行されるすべてのステップをグループ化します。 Each item nested under this section is a separate action or shell script.
185
-
</td>
186
-
</tr>
187
-
<tr>
188
-
<td>
189
-
190
-
```yaml
191
-
- uses: {% data reusables.actions.action-checkout %}
192
-
```
193
-
</td>
194
-
<td>
195
-
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.
196
-
</td>
197
-
</tr>
198
-
<tr>
199
-
<td>
200
-
201
-
```yaml
202
-
- uses: {% data reusables.actions.action-setup-node %}
203
-
with:
204
-
node-version: '14'
205
-
```
206
-
</td>
207
-
<td>
208
-
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>.
この図では、作成したワークフローファイルと、{% 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)」を参照してください。
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 %}.
244
-
245
-
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.actions.workflow-basic-example-and-explanation %}
251
88
252
89
## 次のステップ
253
90
@@ -263,7 +100,8 @@ To understand how billing works for {% data variables.product.prodname_actions %
263
100
264
101
{% data reusables.actions.contacting-support %}
265
102
103
+
{% ifversion ghec or ghes or ghae %}
266
104
## 参考リンク
267
105
268
-
{% ifversion ghec or ghes or ghae %}
269
-
- "[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 %}
106
+
- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"
0 commit comments