| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Remove redundancies:
- Domains
- User/group/project sites
|
| |
|
|
|
| |
This reverts commit 6c75bd015cba181f028bc87c396c3d8e43b5dc3e, reversing
changes made to 1be7f5aaa38aba79843eae8835be6c99c025e982.
|
| |
|
|
| |
Apparently one has to wait, but DNS can't be involved at this step. (As the DNS records had already to be ready and presumably propagated for the ACME challenge to work.) So let's assume it's the content delivery network serving the certificate that needs some time here.
|
| |
|
|
|
| |
Log events so that it's easy to see
when different requests are starting.
|
| |
|
|
|
|
|
| |
Set pages_domain.remove_at when disabling it
Add specs for marking pages domain for removal
Notify user that domain is being removed
Add documentation
|
| |\
| |
| |
| |
| | |
add missing word in docs
See merge request gitlab-org/gitlab-ce!26882
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
docs public key -> private key
See merge request gitlab-org/gitlab-ce!26902
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Git push options to create a merge request, set target_branch and set merge when pipeline succeeds
Closes #53198 and #43263
See merge request gitlab-org/gitlab-ce!26752
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Name GitLab managed apps
See merge request gitlab-org/gitlab-ce!27129
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Fix typo “settings” in Merge requests docs
See merge request gitlab-org/gitlab-ce!27020
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Serverless backend now uses `gitlabktl` tool
Closes #56252 and #58058
See merge request gitlab-org/gitlab-ce!26926
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Show error when namespace/svc account missing
Closes #54506
See merge request gitlab-org/gitlab-ce!26362
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Updated the error message in the docs
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Download a folder from repository
Closes #24704
See merge request gitlab-org/gitlab-ce!26532
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Updated the documentation to match the updated order including
the screenshot.
|
| | | |_|_|/
| |/| | | |
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | | |
This commit updates the documentation about the
"Pipelines must succeed" checkbox.
|
| | | | |
| | | |
| | | |
| | | | |
applications to a Kubernetes cluster"
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
'53459-quick-action-adds-multiple-labels-to-issue-if-middle-words-overlap-with-existing-label' into 'master'
Resolve "Quick Action Adds Multiple Labels to Issue If Middle Words Overlap with Existing Label"
Closes #53459
See merge request gitlab-org/gitlab-ce!26602
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes quick actions add label when adding a label which name middle
word overlaps with another label name: for example adding "A B C" when
also label "B" exists.
With the fix only the label "A B C" is correctly added, previously
also the label "B" was added due to the middle word overlaps.
|
| |/ / / |
|
| | | | |
|
| |/ / |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
A runner installed on a cluster will now use the
cluster's `cluster_type` as its `runner_type`.
|
| |
|
|
|
|
|
|
|
|
|
| |
We are mentioning the commands needed to obtain these fields twice.
Merge them into the single place.
- For API URL we only had the command at the bottom so move this up.
- For CA certificate, we already have the command at the top of the
section
- For Token, we already have an similar command at the top of the
section
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Clarify wiki permissions
Closes #53964
See merge request gitlab-org/gitlab-ce!23044
|
| | | |
|
