| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Revert "Remove HipChat integration from GitLab"
Closes #60042
See merge request gitlab-org/gitlab-ce!27172
|
| | |
| |
| |
| | |
This reverts commit a5378665a1dc0b9c8dc3a4fa279a0eb78aac5aac.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Remove redundancies:
- Domains
- User/group/project sites
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Revert "Merge branch '24704-download-repository-path' into 'master'"
See merge request gitlab-org/gitlab-ce!27249
|
| | | |
| | |
| | |
| | |
| | | |
This reverts commit 6c75bd015cba181f028bc87c396c3d8e43b5dc3e, reversing
changes made to 1be7f5aaa38aba79843eae8835be6c99c025e982.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Process at most 4 pipelines during push
See merge request gitlab-org/gitlab-ce!27205
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
This adds a limitation that we will try to create pipeline
for at most 4 first changes (branches and tags).
This does not affect processing of Pipelines for Merge Requests,
as each updated MR will have associated pipeline created.
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Update Time Tracking feature link
Closes #60164
See merge request gitlab-org/gitlab-ce!27211
|
| | |/ |
|
| | |
| |
| |
| |
| | |
The build in https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/194484356
was failing.
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |/
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
Correct spelling mistake in documentation
See merge request gitlab-org/gitlab-ce!26795
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Documentation for AuthorizedKeysCommand enabled by default in Docker
See merge request gitlab-org/gitlab-ce!27184
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add guide on how to reset runners token
See merge request gitlab-org/gitlab-ce!26829
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Log events so that it's easy to see
when different requests are starting.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Correct screenshot and menu location on housekeeping docs
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Change mode to 644 for doc/ci/variables/img/
See merge request gitlab-org/gitlab-ce!27179
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Update comments about N + 1 Gitaly calls
See merge request gitlab-org/gitlab-ce!27178
|
| | |/ /
| | |
| | |
| | |
| | | |
To make sure all known issues are linked to the correct epic, I've gone
through the code base, and updated the comments where required.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix grammar and try to make clearer how a fork works
See merge request gitlab-org/gitlab-ce!26929
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
add missing word in docs
See merge request gitlab-org/gitlab-ce!26882
|
| | |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Used to get the variables via the API endpoint
`/projects/:id/pipelines/:pipeline_id/variables`
Signed-off-by: Agustin Henze <tin@redhat.com>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | | |
Use RECEIVE namespace rather than REQUEST
See merge request gitlab-org/gitlab-ce!27130
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This brings the mutation type name closer to the associated action,
so the documented example is more consistent.
|
| | | | | | | |
|
| | | | | | | |
|
