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
Co-authored-by: Robert Sese <[email protected]>
Copy file name to clipboardExpand all lines: translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md
Copy file name to clipboardExpand all lines: translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom
135
135
136
136
{% data reusables.user-settings.access_settings %}
intro: 'A private profile displays only limited information, and hides some activity.'
4
+
versions:
5
+
fpt: '*'
6
+
topics:
7
+
- Profiles
8
+
shortTitle: Set profile to private
9
+
---
10
+
11
+
## About private profiles
12
+
13
+
{% note %}
14
+
15
+
**Note:** Private profiles are currently in beta and are subject to change.
16
+
17
+
{% endnote %}
18
+
19
+
To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
20
+
21
+
After making your profile private, you can still view all your information when you visit your own profile.
22
+
23
+
Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
24
+
25
+
## Differences between private and public profiles
26
+
27
+
When your profile is private, the following content is hidden from your profile page:
28
+
29
+
- Achievements and highlights.
30
+
- Activity overview and activity feed.
31
+
- Contribution graph.
32
+
- Follower and following counts.
33
+
- Follow and Sponsor buttons.
34
+
- Organization memberships.
35
+
- Stars, projects, packages, and sponsoring tabs.
36
+
37
+
{% note %}
38
+
39
+
**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
40
+
41
+
{% endnote %}
42
+
43
+
## Changes to reporting on your activities
44
+
45
+
By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
46
+
47
+
When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
48
+
49
+
- Activity feeds for other users.
50
+
- Discussions leaderboards.
51
+
- The [Trending](https://github.com/trending) page.
52
+
53
+
{% note %}
54
+
55
+
**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
56
+
57
+
{% endnote %}
58
+
59
+
## Changing your profile's privacy settings
60
+
61
+
{% data reusables.user-settings.access_settings %}
62
+
1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
63
+
{% data reusables.user-settings.update-preferences %}
Copy file name to clipboardExpand all lines: translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ You can configure a job's dependencies with other jobs; by default, jobs have no
72
72
73
73
For more information about jobs, see "[Using jobs](/actions/using-jobs)."
74
74
75
-
### アクション
75
+
### Actions
76
76
77
77
An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task. Use an action to help reduce the amount of repetitive code that you write in your workflow files. An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
Copy file name to clipboardExpand all lines: translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
104
104
```
105
105
{% endraw %}
106
106
For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
107
-
1. Reference the input or secret in the reusable workflow.
107
+
1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
Copy file name to clipboardExpand all lines: translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+22-20Lines changed: 22 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -370,13 +370,15 @@ topics:
370
370
|`gist.destroy`| A gist is deleted. |
371
371
|`gist.visibility_change`| The visibility of a gist is changed. |
372
372
373
+
{% ifversion ghec or ghes > 3.4 or ghae-issue-6724 %}
|`pull_request.close`| A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." |
862
-
|`pull_request.converted_to_draft`| A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." |
863
-
|`pull_request.create`| A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." |
864
-
|`pull_request.create_review_request`| A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."|
865
-
|`pull_request.in_progress`| A pull request was marked as in progress. |
866
-
|`pull_request.indirect_merge`| A pull request was considered merged because the pull request's commits were merged into the target branch. |
867
-
|`pull_request.merge`| A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 |
868
-
|`pull_request.ready_for_review`| A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)."|
869
-
|`pull_request.remove_review_request`| A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."|
870
-
|`pull_request.reopen`| A pull request was reopened after previously being closed. |
871
-
|`pull_request_review.delete`| A review on a pull request was deleted. |
872
-
|`pull_request_review.dismiss`| A review on a pull request was dismissed. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 |
873
-
|`pull_request_review.submit`| A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."|
|`pull_request.close`| A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." |
864
+
|`pull_request.converted_to_draft`| A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." |
865
+
|`pull_request.create`| A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." |
866
+
|`pull_request.create_review_request`| A review was requested on a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 |
867
+
|`pull_request.in_progress`| A pull request was marked as in progress. |
868
+
|`pull_request.indirect_merge`| A pull request was considered merged because the pull request's commits were merged into the target branch. |
869
+
|`pull_request.merge`| A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 |
870
+
|`pull_request.ready_for_review`| A pull request was marked as ready for review. 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)」を参照してください。 |
871
+
|`pull_request.remove_review_request`| A review request was removed from a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 |
872
+
|`pull_request.reopen`| A pull request was reopened after previously being closed. |
873
+
|`pull_request_review.delete`| A review on a pull request was deleted. |
874
+
|`pull_request_review.dismiss`| A review on a pull request was dismissed. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 |
875
+
|`pull_request_review.submit`| A review was submitted for a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 |
|`pull_request_review_comment.create`| A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."|
888
-
|`pull_request_review_comment.delete`| A review comment on a pull request was deleted. |
889
-
|`pull_request_review_comment.update`| A review comment on a pull request was changed. |
|`pull_request_review_comment.create`| A review comment was added to a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。|
890
+
|`pull_request_review_comment.delete`| A review comment on a pull request was deleted. |
891
+
|`pull_request_review_comment.update`| A review comment on a pull request was changed. |
Copy file name to clipboardExpand all lines: translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,7 +160,7 @@ C/C++、C#、Go、Javaなどのコンパイル言語については、{% data va
160
160
161
161
成果物には、{% data variables.product.prodname_codeql %}によってスキャンされたソースのアーカイブされたコピーが_src.zip_という名前で含まれます。 リポジトリ中のソースコードファイルと_src.zip_中のファイルを比較すれば、どういった種類のファイルが欠けているかが分かります。 分析されなかったファイルの種類が分かれば、{% data variables.product.prodname_codeql %}分析のためのワークフローをどのように変更しなければならないかは簡単に理解できるようになります。
162
162
163
-
## Alerts found in generated code
163
+
## 生成されたコードで見つかったアラート
164
164
165
165
{% data reusables.code-scanning.alerts-found-in-generated-code %}
0 commit comments