| Age | Commit message (Collapse) | Author |
|---|
|
|
|
As part of https://gitlab.com/gitlab-org/gitlab-ee/issues/8910,
all occurrences of License Management are replace with
License Compliance.
|
|
|
|
|
|
Addressing a documentation review by Marcia!
|
|
Removed duplicate Live preview entry for MR docs
See merge request gitlab-org/gitlab-ce!31763
|
|
|
|
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31068 forgot to
add a short description of the new push options that it added.
|
|
|
|
|
|
Align images and lists in assorted markdown docs
|
|
Replace redirect_from with disqus_identifier in docs
See merge request gitlab-org/gitlab-ce!31595
|
|
Adds MD010 (Hard tabs), MD012 (blank lines), MD029 (ordered
list prefix), MD030 (spaces after list markers), and fixes
remaining docs that were failing these tests
|
|
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
|
|
Let's use disqus_identifier since this is a more
descriptive name. We will need redirect_from for
another purpose anyway (Nanoc redirects).
|
|
|
|
Documents how to enable security approvals
|
|
Support title and desc on merge w/ push option
See merge request gitlab-org/gitlab-ce!31068
|
|
|
|
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
|
|
Support remove source branch on merge w/ push options
See merge request gitlab-org/gitlab-ce!30728
|
|
This feature needs to be documented, so here is the documentation
|
|
|
|
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.
|
|
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
|
|
|
|
|
|
This updates redirected links in integration, update, user
and workflow dirs. Should now link to final URLs to avoid
redirect hops
|
|
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
|
|
After review, heading was changed and links to
it needed to be updated, and minor tweaks to
the issues docs such as note formatting
|
|
Add backticks around square brackets, or fix links, as necessary.
|
|
|
|
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.
|
|
Also adds and one linting rule
and makes project conform to it.
|
|
- 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
|
|
Signed-off-by: William Desportes <williamdes@wdes.fr>
|
|
doc: add git mr command promotion
See merge request gitlab-org/gitlab-ce!28860
|
|
|
|
|
|
|
|
|
|
"Checkout locally by adding a git alias" needs small change
See merge request gitlab-org/gitlab-ce!28330
|
|
|
|
|
|
|
|
This feature was introduced in 12.0, not in 11.11.
|
|
|
|
|
|
This backports API and quick action docs.
|
|
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
|
