Skip to content

repo sync #17279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Octomerger merged 2 commits into from
Apr 21, 2022
Merged

repo sync #17279

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
487f19c
New translation batch for ja (#27134)
docubot Apr 21, 2022
9c4e8f2
Merge branch 'main' into repo-sync
Octomerger Apr 21, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
1 change: 1 addition & 0 deletions ...e/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,5 +17,6 @@ children:
- /personalizing-your-profile
- /managing-your-profile-readme
- /pinning-items-to-your-profile
- /setting-your-profile-to-private
---

2 changes: 1 addition & 1 deletion ...ging-your-github-profile/customizing-your-profile/personalizing-your-profile.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom

{% data reusables.user-settings.access_settings %}
2. [Profile settings] で、無効にするバッジの選択を解除します。 ![プロフィールでバッジを非表示にするチェックボックス](/assets/images/help/profile/profile-badge-settings.png)
3. [**Update preferences**] をクリックします。
{% data reusables.user-settings.update-preferences %}

{% endif %}

Expand Down
63 changes: 63 additions & 0 deletions ...your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: Setting your profile to private
intro: 'A private profile displays only limited information, and hides some activity.'
versions:
fpt: '*'
topics:
- Profiles
shortTitle: Set profile to private
---

## About private profiles

{% note %}

**Note:** Private profiles are currently in beta and are subject to change.

{% endnote %}

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.

After making your profile private, you can still view all your information when you visit your own profile.

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.

## Differences between private and public profiles

When your profile is private, the following content is hidden from your profile page:

- Achievements and highlights.
- Activity overview and activity feed.
- Contribution graph.
- Follower and following counts.
- Follow and Sponsor buttons.
- Organization memberships.
- Stars, projects, packages, and sponsoring tabs.

{% note %}

**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.

{% endnote %}

## Changes to reporting on your activities

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.

When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:

- Activity feeds for other users.
- Discussions leaderboards.
- The [Trending](https://github.com/trending) page.

{% note %}

**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.

{% endnote %}

## Changing your profile's privacy settings

{% data reusables.user-settings.access_settings %}
1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
{% data reusables.user-settings.update-preferences %}
2 changes: 1 addition & 1 deletion ...ions/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ You can configure a job's dependencies with other jobs; by default, jobs have no

For more information about jobs, see "[Using jobs](/actions/using-jobs)."

### アクション
### Actions

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.

Expand Down
2 changes: 1 addition & 1 deletion translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
```
{% endraw %}
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).
1. Reference the input or secret in the reusable workflow.
1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.

{% raw %}
```yaml
Expand Down
42 changes: 22 additions & 20 deletions ...eviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -370,13 +370,15 @@ topics:
| `gist.destroy` | A gist is deleted. |
| `gist.visibility_change` | The visibility of a gist is changed. |

{% ifversion ghec or ghes > 3.4 or ghae-issue-6724 %}
### `git` カテゴリアクション

| アクション | 説明 |
| ----------- | --------------------------------------- |
| `git.clone` | A repository was cloned. |
| `git.fetch` | Changes were fetched from a repository. |
| `git.push` | Changes were pushed to a repository. |
{% endif %}

### `hook` カテゴリアクション

Expand Down Expand Up @@ -856,21 +858,21 @@ topics:
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
### `pull_request`カテゴリのアクション

| アクション | 説明 |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `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)." |
| `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)." |
| `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)." |
| `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)." |
| `pull_request.in_progress` | A pull request was marked as in progress. |
| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. |
| `pull_request.merge` | A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 |
| `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)." |
| `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)." |
| `pull_request.reopen` | A pull request was reopened after previously being closed. |
| `pull_request_review.delete` | A review on a pull request was deleted. |
| `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)を参照してください。 |
| `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)." |
| `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)." |
| `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)." |
| `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)」を参照してください。 |
| `pull_request.in_progress` | A pull request was marked as in progress. |
| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. |
| `pull_request.merge` | A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 |
| `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)」を参照してください。 |
| `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)」を参照してください。 |
| `pull_request.reopen` | A pull request was reopened after previously being closed. |
| `pull_request_review.delete` | A review on a pull request was deleted. |
| `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)を参照してください。 |
| `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`カテゴリのアクション

Expand All @@ -882,11 +884,11 @@ topics:

### `pull_request_review_comment`カテゴリのアクション

| アクション | 説明 |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `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)." |
| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
| `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)」を参照してください。 |
| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
| `pull_request_review_comment.update` | A review comment on a pull request was changed. |
{%- endif %}

### `repo` カテゴリアクション
Expand Down
2 changes: 1 addition & 1 deletion ...your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ C/C++、C#、Go、Javaなどのコンパイル言語については、{% data va

成果物には、{% data variables.product.prodname_codeql %}によってスキャンされたソースのアーカイブされたコピーが_src.zip_という名前で含まれます。 リポジトリ中のソースコードファイルと_src.zip_中のファイルを比較すれば、どういった種類のファイルが欠けているかが分かります。 分析されなかったファイルの種類が分かれば、{% data variables.product.prodname_codeql %}分析のためのワークフローをどのように変更しなければならないかは簡単に理解できるようになります。

## Alerts found in generated code
## 生成されたコードで見つかったアラート

{% data reusables.code-scanning.alerts-found-in-generated-code %}

Expand Down
Loading