- 09 7月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
This updates redirected links in integration, update, user and workflow dirs. Should now link to final URLs to avoid redirect hops
-
- 08 7月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
Previously, we used brackets to denote the tier badges, but this made Kramdown, the docs site Markdown renderer, show many warnings when building the site. This is now fixed by using parentheses instead of square brackets. This was caused by [PREMIUM] looking like a link to Kramdown, which couldn't find a URL there. See: - https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484 - https://gitlab.com/gitlab-org/gitlab-ce/issues/63800
-
- 04 7月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
After review, heading was changed and links to it needed to be updated, and minor tweaks to the issues docs such as note formatting
-
- 03 7月, 2019 2 次提交
-
-
由 Marcel Amirault 提交于
Add backticks around square brackets, or fix links, as necessary.
-
由 John Woods 提交于
-
- 25 6月, 2019 2 次提交
-
-
由 Fabio Pitino 提交于
When a user sets only_allow_merge_if_pipeline_succeeds, also named as "Pipeline must succeed" project setting, we require the pipeline to be present. This solves race condition issues especially with external CI providers when a build is triggered externally but no pipelines are created in GitLab yet. Document that a head pipeline is expected when using "Pipeline must succeed" setting. Also explain limitations with the use of only/except where there may not be any jobs created and the merge request will not be allowed to be merged.
-
由 Evan Read 提交于
Also adds and one linting rule and makes project conform to it.
-
- 10 6月, 2019 1 次提交
-
-
由 Achilleas Pipinellis 提交于
- Edit pages under user/project/merge_requests and add the relevant types in the frontmatter. - Clean up descriptions. Based on https://gitlab.com/groups/gitlab-org/-/epics/1280
-
- 07 6月, 2019 1 次提交
-
-
由 William Desportes 提交于
Signed-off-by: NWilliam Desportes <williamdes@wdes.fr>
-
- 05 6月, 2019 1 次提交
-
-
由 PatOnTheBack 提交于
-
- 04 6月, 2019 1 次提交
-
-
由 Mark Chao 提交于
-
- 31 5月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 29 5月, 2019 1 次提交
-
-
由 Elan Ruusamäe 提交于
-
- 21 5月, 2019 1 次提交
-
-
由 Achilleas Pipinellis 提交于
-
- 18 5月, 2019 1 次提交
-
-
由 Lucas Charles 提交于
-
- 17 5月, 2019 2 次提交
-
-
由 Marcel Amirault 提交于
-
由 Achilleas Pipinellis 提交于
This feature was introduced in 12.0, not in 11.11.
-
- 15 5月, 2019 1 次提交
-
-
由 Brett Walker 提交于
-
- 05 5月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 01 5月, 2019 1 次提交
-
-
由 Oswaldo Ferreira 提交于
This backports API and quick action docs.
-
- 09 4月, 2019 2 次提交
-
-
由 Luke Duncalfe 提交于
MergeRequests::PushOptionsHandlerService has been updated to allow creating and updating merge requests with the `merge_when_pipeline_succeeds` set using git push options. To create a new merge request and set it to merge when the pipeline succeeds: git push -u origin -o merge_request.create \ -o merge_request.merge_when_pipeline_succeeds To update an existing merge request and set it to merge when the pipeline succeeds: git push -u origin -o merge_request.merge_when_pipeline_succeeds Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/53198
-
由 Luke Duncalfe 提交于
To create a new merge request: git push -u origin -o merge_request.create To create a new merge request setting target branch: git push -u origin -o merge_request.create \ -o merge_request.target=123 To update an existing merge request with a new target branch: git push -u origin -o merge_request.target=123 A new Gitlab::PushOptions class handles parsing and validating the push options array. This can be the start of the standard of GitLab accepting push options that follow namespacing rules. Rules are discussed in issue https://gitlab.com/gitlab-org/gitlab-ce/issues/43263. E.g. these push options: -o merge_request.create -o merge_request.target=123 Become parsed as: { merge_request: { create: true, target: '123', } } And are fetched with the class via: push_options.get(:merge_request) push_options.get(:merge_request, :create) push_options.get(:merge_request, :target) A new MergeRequests::PushOptionsHandlerService takes the `merge_request` namespaced push options and handles creating and updating merge requests. Any errors encountered are passed to the existing `output` Hash in Api::Internal's `post_receive` endpoint, and passed to gitlab-shell where they're output to the user. Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/43263
-
- 05 4月, 2019 1 次提交
-
-
由 Rory O’Kane 提交于
-
- 04 4月, 2019 1 次提交
-
-
由 Nathan Friend 提交于
This commit updates the documentation about the "Pipelines must succeed" checkbox.
-
- 02 4月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 27 3月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 22 3月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 20 3月, 2019 1 次提交
-
-
由 Evan Read 提交于
-
- 15 3月, 2019 1 次提交
-
-
由 Evan Read 提交于
- Also has other minor improvements.
-
- 07 3月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 07 2月, 2019 1 次提交
-
-
由 Natalia Tepluhina 提交于
-
- 06 2月, 2019 2 次提交
-
-
由 Luke Duncalfe 提交于
-
由 Evan Read 提交于
-
- 25 1月, 2019 1 次提交
-
-
由 Sam Bigelow 提交于
this is to match `git branch -D` from https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23966 This just documents the change
-
- 22 1月, 2019 1 次提交
-
-
由 Marcia Ramos 提交于
-
- 17 1月, 2019 1 次提交
-
-
由 Achilleas Pipinellis 提交于
-
- 08 1月, 2019 2 次提交
-
-
由 Evan Read 提交于
- Also makes other minor Markdown fixes that were near the main fixes.
-
由 Brett Walker 提交于
-
- 18 12月, 2018 2 次提交
-
-
由 Achilleas Pipinellis 提交于
-
由 Jacques Erasmus 提交于
-