@@ -486,11 +486,9 @@ introduced by [#25381](https://gitlab.com/gitlab-org/gitlab/-/issues/25381).
...
@@ -486,11 +486,9 @@ introduced by [#25381](https://gitlab.com/gitlab-org/gitlab/-/issues/25381).
### Batch Suggestions
### Batch Suggestions
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/25486) in GitLab 13.1 as an [alpha feature](https://about.gitlab.com/handbook/product/gitlab-the-product/#alpha).
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/25486) in GitLab 13.1 as an [alpha feature](https://about.gitlab.com/handbook/product/gitlab-the-product/#alpha) behind a feature flag, disabled by default.
> - Deployed behind a feature flag, disabled by default.
> - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/227799) in GitLab 13.2.
> - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/227799) in GitLab 13.2.
> - Enabled on GitLab.com.
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/320755) in GitLab 13.11.
> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-batch-suggestions).
You can apply multiple suggestions at once to reduce the number of commits added
You can apply multiple suggestions at once to reduce the number of commits added
to your branch to address your reviewers' requests.
to your branch to address your reviewers' requests.
...
@@ -540,7 +538,7 @@ You can assign an issue to a user who made a comment.
...
@@ -540,7 +538,7 @@ You can assign an issue to a user who made a comment.
In the comment, click the **More Actions** menu and click **Assign to commenting user**.
In the comment, click the **More Actions** menu and click **Assign to commenting user**.
Click the button again to unassign the commenter.
Click the button again to unassign the commenter.
![Assign to commenting user](img/quickly_assign_commenter_v13_1.png)
![Assign to commenting user](img/quickly_assign_commenter_v13_1.png)
...
@@ -562,24 +560,3 @@ To disable it:
...
@@ -562,24 +560,3 @@ To disable it:
```ruby
```ruby
Feature.disable(:confidential_notes)
Feature.disable(:confidential_notes)
```
```
## Enable or disable Batch Suggestions **(FREE SELF)**
Batch Suggestions is
deployed behind a feature flag that is **enabled by default**.
[GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md)
@@ -18,38 +18,39 @@ and is automatically configured on [GitHub import](../../../integration/github.m
...
@@ -18,38 +18,39 @@ and is automatically configured on [GitHub import](../../../integration/github.m
## Configuration
## Configuration
### Complete these steps on GitHub
This integration requires a [GitHub API token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token)
This integration requires a [GitHub API token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token)
with `repo:status` access granted:
with `repo:status` access granted.
Complete these steps on GitHub:
1. Go to your "Personal access tokens" page at <https://github.com/settings/tokens>
1. Go to your **Personal access tokens** page at <https://github.com/settings/tokens>.
1. Click "Generate New Token"
1. Select **Generate new token**.
1. Ensure that `repo:status` is checked and click "Generate token"
1. Under **Note**, enter a name for the new token.
1. Copy the generated token to use on GitLab
1. Ensure that `repo:status` is checked and select **Generate token**.
1. Copy the generated token to use in GitLab.
### Complete these steps on GitLab
Complete these steps in GitLab:
1.Navigate to the project you want to configure.
1.Go to the project you want to configure.
1.Navigate to the [Integrations page](overview.md#accessing-integrations)
1.Go to the [Integrations page](overview.md#accessing-integrations)
1.Click "GitHub".
1.Select **GitHub**.
1. Ensure that the **Active** toggle is enabled.
1. Ensure that the **Active** toggle is enabled.
1. Paste the token you've generated on GitHub
1. Paste the token you generated on GitHub.
1. Enter the path to your project on GitHub, such as `https://github.com/username/repository`
1. Enter the path to your project on GitHub, such as `https://github.com/username/repository`.
1.Optionally uncheck **Static status check names** checkbox to disable static status check names.
1.(Optional) To disable static status check names, clear the **Static status check names** checkbox.
1. Save or optionally click "Test Settings".
1. Select **Save changes** or optionally select **Test settings**.
Once the integration is configured, see [Pipelines for external pull requests](../../../ci/ci_cd_for_external_repos/#pipelines-for-external-pull-requests)
After configuring the integration, see [Pipelines for external pull requests](../../../ci/ci_cd_for_external_repos/#pipelines-for-external-pull-requests)
to configure pipelines to run for open pull requests.
to configure pipelines to run for open pull requests.
#### Static / dynamic status check names
### Static / dynamic status check names
> - Introduced in GitLab 11.5: using static status check names as opt-in option.
> - Introduced in GitLab 11.5: using static status check names as opt-in option.
> - [In GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/issues/9931), static status check names is default behavior for new projects.
> - [In GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/issues/9931), static status check names is default behavior for new projects.
This makes it possible to mark these status checks as _Required_ on GitHub.
This makes it possible to mark these status checks as **Required** on GitHub.
With **Static status check names** enabled on the integration page, your
GitLab instance host name is appended to a status check name,
When **Static status check names** is enabled on the integration page, your
whereas in case of dynamic status check names, a branch name is appended.
GitLab instance host name is appended to a status check name.
static_context_field_help=s_('GithubIntegration|Select this if you want GitHub to mark status checks as "Required". %{learn_more_link_start}Learn more%{learn_more_link_end}.').html_safe%{learn_more_link_start: learn_more_link_start,learn_more_link_end: '</a>'.html_safe}
token_field_help=s_('GithubIntegration|Create a %{token_link_start}personal access token%{token_link_end} with %{status_html} access granted and paste it here.').html_safe%{token_link_start: token_link_start,token_link_end: '</a>'.html_safe,status_html: '<code>repo:status</code>'.html_safe}
[
[
{type: 'password',
{type: 'password',
name: "token",
name: "token",
required: true,
required: true,
placeholder: "e.g. 8d3f016698e...",
placeholder: "8d3f016698e...",
help: 'Create a <a href="https://github.com/settings/tokens">personal access token</a> with <code>repo:status</code> access granted and paste it here.'.html_safe},
msgid "GithubIntegration|Create a %{token_link_start}personal access token%{token_link_end} with %{status_html} access granted and paste it here."
msgstr ""
msgid "GithubIntegration|Obtain statuses for commits and pull requests."
msgstr ""
msgid "GithubIntegration|Repository URL"
msgstr ""
msgid "GithubIntegration|Select this if you want GitHub to mark status checks as \"Required\". %{learn_more_link_start}Learn more%{learn_more_link_end}."
msgstr ""
msgid "GithubIntegration|Static status check names (optional)"
msgstr ""
msgid "GithubIntegration|This requires mirroring your GitHub repository to this project. %{docs_link}"
msgstr ""
msgid "Gitlab Pages"
msgid "Gitlab Pages"
msgstr ""
msgstr ""
...
@@ -16709,9 +16727,6 @@ msgstr ""
...
@@ -16709,9 +16727,6 @@ msgstr ""
msgid "Integrations|This integration, and inheriting projects were reset."
msgid "Integrations|This integration, and inheriting projects were reset."
msgstr ""
msgstr ""
msgid "Integrations|This requires mirroring your GitHub repository to this project. %{docs_link}"
msgstr ""
msgid "Integrations|To keep this project going, create a new issue."
msgid "Integrations|To keep this project going, create a new issue."