- 06 9月, 2019 2 次提交
-
-
由 Christian Couder 提交于
-
由 Russell Dickenson 提交于
-
- 04 9月, 2019 1 次提交
-
-
由 Christian Couder 提交于
MergeRequests::PushOptionsHandlerService has been updated to allow adding and removing labels to a merge request using git push options. To create a new merge request and add 2 labels to it: git push -u origin -o merge_request.create \ -o merge_request.label="My label 1" \ -o merge_request.label="My label 2" To update an existing merge request and remove a label while adding a different label: git push -u origin -o merge_request.label="My added label" \ -o merge_request.unlabel="My removed label" Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/64320
-
- 02 9月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
Also fix links to renamed headers and moved content
-
- 28 8月, 2019 1 次提交
-
-
由 Achilleas Pipinellis 提交于
- New redirect doc/user/application_security/license_compliance/index.md - Renaming of images. - Some links that were pointing to the old location are fixed.
-
- 22 8月, 2019 1 次提交
-
-
由 Achilleas Pipinellis 提交于
As part of https://gitlab.com/gitlab-org/gitlab-ee/issues/8910, all occurrences of License Management are replace with License Compliance.
-
- 20 8月, 2019 1 次提交
-
-
由 Samantha Ming 提交于
-
- 15 8月, 2019 1 次提交
-
-
由 Christian Couder 提交于
-
- 14 8月, 2019 1 次提交
-
-
由 Christian Couder 提交于
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31068 forgot to add a short description of the new push options that it added.
-
- 13 8月, 2019 1 次提交
-
-
由 Philipp Hasper 提交于
-
- 09 8月, 2019 1 次提交
-
-
由 Nick Thomas 提交于
We're removing the ability for MRs in a single project to block each other, and performing a rename of the feature to go along with that. This necessitates documentation changes
-
- 24 7月, 2019 1 次提交
-
-
由 Christian Couder 提交于
MergeRequests::PushOptionsHandlerService has been updated to allow creating and updating merge requests with the `title` and `description` set using git push options. To create a new merge request and set its title and description: git push -u origin -o merge_request.create \ -o merge_request.title="My title" \ -o merge_request.description="My description" To update an existing merge request and set its title and description: git push -u origin -o merge_request.title="My title" \ -o merge_request.description="My description" Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/64320
-
- 22 7月, 2019 1 次提交
-
-
由 Nick Thomas 提交于
This feature needs to be documented, so here is the documentation
-
- 19 7月, 2019 1 次提交
-
-
由 James Ramsay 提交于
-
- 18 7月, 2019 1 次提交
-
-
由 Patrick Bajao 提交于
Add a section in Confidential Issues documentation with information about the "Create confidential merge request" button/dropdown and how it can help in resolving confidential issues.
-
- 17 7月, 2019 1 次提交
-
-
由 Christian Couder 提交于
MergeRequests::PushOptionsHandlerService has been updated to allow creating and updating merge requests with the `remove_source_branch` set using git push options. To create a new merge request and set it to remove the source branch when it is merged: git push -u origin -o merge_request.create \ -o merge_request.remove_source_branch To update an existing merge request and set it to remove the source branch when it is merged: git push -u origin -o merge_request.remove_source_branch Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/64320
-
- 15 7月, 2019 1 次提交
-
-
由 Michel Engelen 提交于
-
- 10 7月, 2019 1 次提交
-
-
由 Christian Couder 提交于
-
- 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
-
- 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>
-
- 31 5月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 29 5月, 2019 1 次提交
-
-
由 Elan Ruusamäe 提交于
-
- 21 5月, 2019 1 次提交
-
-
由 Achilleas Pipinellis 提交于
-
- 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 提交于
-
- 27 3月, 2019 1 次提交
-
-
由 Marcel Amirault 提交于
-
- 06 2月, 2019 1 次提交
-
-
由 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 1 次提交
-
-
由 Jacques Erasmus 提交于
-
- 07 12月, 2018 1 次提交
-
-
由 Marcia Ramos 提交于
-