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
Copy file name to clipboardexpand all lines: doc/api/merge_requests.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -652,7 +652,7 @@ Supported attributes:
652
652
|`latest_build_finished_at`| datetime | Timestamp of when the latest build for the merge request finished. |
653
653
|`latest_build_started_at`| datetime | Timestamp of when the latest build for the merge request started. |
654
654
|`merge_commit_sha`| string | SHA of the merge request commit. Returns `null` until merged. |
655
-
|`merge_error`| string | Error message due to a merge error.|
655
+
|`merge_error`| string | Error message shown when a merge has failed. To check mergeability, use `detailed_merge_status` instead |
656
656
|`merge_user`| object | The user who merged this merge request, the user who set it to merge when pipeline succeeds, or `null`. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349031) in GitLab 14.7. |
657
657
|`merge_status`| string | Status of the merge request. Can be `unchecked`, `checking`, `can_be_merged`, `cannot_be_merged`, or `cannot_be_merged_recheck`. Affects the `has_conflicts` property. For important notes on response data, read [Single merge request response notes](#single-merge-request-response-notes). [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/3169#note_1162532204) in GitLab 15.6. Use `detailed_merge_status` instead. |
658
658
|`merge_when_pipeline_succeeds`| boolean | Indicates if the merge has been set to be merged when its pipeline succeeds. |
Copy file name to clipboardexpand all lines: doc/ci/runners/configure_runners.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -637,13 +637,12 @@ test:
637
637
- pwd
638
638
```
639
639
640
-
The `GIT_CLONE_PATH` has to always be within `$CI_BUILDS_DIR`. The directory set in `$CI_BUILDS_DIR`
640
+
The `GIT_CLONE_PATH` must always be within `$CI_BUILDS_DIR`. The directory set in `$CI_BUILDS_DIR`
641
641
is dependent on executor and configuration of [runners.builds_dir](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-section)
642
642
setting.
643
643
644
644
This can only be used when `custom_build_dir` is enabled in the
Copy file name to clipboardexpand all lines: doc/development/gitlab_flavored_markdown/index.md
+2
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ group: Editor
4
4
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
Copy file name to clipboardexpand all lines: doc/development/gitlab_flavored_markdown/specification_guide/index.md
+2
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ group: Editor
4
4
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
raiseAmbigiousSpecificationError,"`#{masked_location(location.to_json)}` does not have a valid subkey for include. Valid subkeys are: `#{FILE_SUBKEYS.join('`, `')}`"
141
-
else
142
-
raiseAmbigiousSpecificationError,"Each include must use only one of: `#{FILE_SUBKEYS.join('`, `')}`"
143
-
end
144
-
end
145
-
146
-
defverify!(location_object)
147
-
verify_max_includes!
148
-
location_object.validate!
149
-
expandset.add(location_object)
150
-
end
151
-
152
-
defverify_max_includes!
153
-
ifexpandset.count >= context.max_includes
154
-
raiseTooManyIncludesError,"Maximum of #{context.max_includes} nested includes are allowed!"
0 commit comments