| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Backports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10161
(code out of ee/ folder).
|
|
|
|
|
|
| |
MWPSService currently uses the old pipeline lookup method. It searches
related merge requests with pipeline.ref, however, this doesn't work
for attached/detached merge request pipelines.
|
|
|
|
| |
Backport changes to CE
|
|
|
|
|
|
|
|
|
|
| |
and add spec
Add changelog
ok
ok
|
|\
| |
| |
| |
| |
| |
| | |
Use merge request HEAD ref for detached merge request pipelines
Closes #58454
See merge request gitlab-org/gitlab-ce!25504
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By using `refs/merge-requests/:iid/head`
ok
ok
Improve naming nicely
Add nice tests
add nice tests
fix some more
revert
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Allow external diffs to be used conditionally
Closes #54670
See merge request gitlab-org/gitlab-ce!25432
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since external diffs are likely to be a bit slower than in-database
ones, add a mode that makes diffs external after they've been obsoleted
by events. This should strike a balance between performance and disk
space.
A background cron drives the majority of migrations, since diffs become
outdated through user actions.
|
|\ \
| |/
|/|
| |
| | |
Prepares suggestion implementation for multi-line support
See merge request gitlab-org/gitlab-ce!26057
|
| |
| |
| |
| |
| |
| | |
Adds the groundwork needed in order to persist multi-line suggestions,
while providing the parsing strategy which will be reused for the
**Preview** as well.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Error messages from custom pre-receive hooks now appear in the GitLab
UI.
This is re-enabling a feature that had been disabled in merge request
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18646
The feature had been disabled due to security concerns that information
which was not intended to be public (like stack traces) would leak into
public view.
PreReceiveErrors (from pre-receive, post-receive and update custom
hooks) are now filtered for messages that have been prefixed in a
particular way.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/48132
|
|
|
|
| |
Fixes #56864
|
|
|
| |
This reverts merge request !25708
|
|
|
|
|
| |
Returns the source and target IDs used to create
the merge commit on Gitaly.
|
| |
|
|\ |
|
| |\
| | |
| | |
| | |
| | | |
[master] Check issue milestone availability
See merge request gitlab/gitlabhq!2788
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add project when creating milestone in specs
We validate milestone is from the same
project/parent group as issuable ->
we need to set project in specs correctly
Improve methods names and specs organization
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a merge fails due to a locked file, no feedback was given to the
user as to why it failed if the user used the Merge button. However, if
the push attempt happened directly in the Web UI, the pre-receive
message would be displayed.
To be consistent and to make it clear why a merge failed, we now include
the pre-receive error message in the merge request widget.
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/10165
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix
ok
Add spec
Fix
ok
Fix
Add changelog
Fix
Add memoization
a
fix
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Returns error in MergeToRefService when
merge_to_tmp_merge_ref_path ff is disabled.
|
| |
| |
| |
| |
| | |
Move authorization checks to merge services
instead relying solely on external checks.
|
|/
|
|
|
|
|
|
| |
Adds the ground work for writing into
the merge ref refs/merge-requests/:iid/merge the
merge result between source and target branches of
a MR, without further side-effects such as
mailing, MR updates and target branch changes.
|
|
|
|
| |
Allow single tasks to be updated quickly
|
| |
|
| |
|
|
|
|
| |
Sort out some logic
|
|\
| |
| |
| |
| | |
Bump Ruby on Rails to 5.0.7.1
See merge request gitlab-org/gitlab-ce!23396
|
| |
| |
| |
| | |
Fix the CVE-2018-16476 vulnerability.
|
|\ \
| | |
| | |
| | |
| | | |
[master] Validate projects in MR build service
See merge request gitlab/gitlabhq!2678
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This validates the correct abilities for both projects. Only
`read_project` isn't enough:
For the `source_project` we validate `create_merge_request_from` this
also validates that the user has developer access to the project.
For the `target_project` we validate `create_merge_reqeust_in` this
also validates that the user has access to the project's repository.
To avoid generating diffs for unrelated projects we also validate that
the projects are in the same fork network now.
|
|/
|
|
|
| |
These can just be `delete` calls, with the caveat that it only takes one
argument.
|
| |
|
|
|
|
|
|
|
|
|
| |
Analyze new commits graph to determine each commit's merge commit.
Fix "merged with [commit]" info for merge requests being merged
automatically by other actions.
Allow analyzing upto the relevant commit
|
| |
|
|
|
|
|
|
|
|
|
| |
Creating a merge request with
`merge_request[force_remove_source_branch]` parameter would result in an
Error 500 since this attribute was passed directly to the merge request.
Fix this by properly parsing this attribute into `merge_params`.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/51220
|
|\
| |
| |
| |
| |
| |
| | |
Resolve "Add a `/create_merge_request` quick action"
Closes #40085
See merge request gitlab-org/gitlab-ce!22485
|
| |
| |
| |
| |
| |
| |
| | |
With this quick action the user can create a new MR starting from
the current issue using as `source_branch` the given `branch name` and
as `target_branch` the project default branch. If the `branch name` is
omitted a name is automatically created starting from the issue title.
|
|/ |
|
|
|
|
|
| |
This reverts commit a82a595728d54bdc12e51dfcfb22e9eddc449143, reversing
changes made to e7df959b8f99875edd246c7ac7779c3203e8755e.
|
|\
| |
| |
| |
| |
| |
| | |
Allow to add patches to merge requests created via email
Closes #40830
See merge request gitlab-org/gitlab-ce!22723
|
| |
| |
| |
| |
| |
| | |
Sometimes we don't want to trigger any quick actions that cause side
effects. For example when building a record to validate. This allows
listing the quick actions that need to be performed.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows users to add patches as attachments to merge request
created via email.
When an email to create a merge request is sent, all the attachments
ending in `.patch` will be applied to the branch specified in the
subject of the email. If the branch did not exist, it will be created
from the HEAD of the repository.
When the patches could not be applied, the error message will be
replied to the user.
The patches can have a maximum combined size of 2MB for now.
|
|/
|
|
|
| |
'master'"
This reverts merge request !22526
|
|\
| |
| |
| |
| | |
Comment on any expanded diff line on MRs
See merge request gitlab-org/gitlab-ce!22398
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In EE, there is need to call `merge_requests_for_source_branch`
before calling CE's `refresh_merge_requests,
in order to obtain the old diffs.
However that requires `@push`,
initialized inside CE's refresh_merge_requests.
However it can't be set early in EE, or static analysis would fail
because use of instance variables in module is discouraged.
So @push is set in execute instead.
|