| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| | |
Add enabled prefix to feature keys to be consistent with other keys
See merge request gitlab-org/gitlab-ce!20043
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Properly detect label reference if followed by period or question mark
See merge request gitlab-org/gitlab-ce!19965
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rails 5 fix Capybara::ElementNotFound: Unable to find visible css #modal-revert-commit
Closes #48140 et #48139
See merge request gitlab-org/gitlab-ce!20044
|
| | | |
| | | |
| | | |
| | | | |
#modal-revert-commit and expected: "/bar" got: "/foo"
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Raw changes calculation is Gitaly only now
Closes gitaly#1138
See merge request gitlab-org/gitlab-ce!20057
|
| | | | |
| | | | |
| | | | |
| | | | | |
Closes https://gitlab.com/gitlab-org/gitaly/issues/1138
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add a cop for `FinderMethods`
Closes #42705
See merge request gitlab-org/gitlab-ce!19951
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This notifies developers when calling `find(_by!)` chained on
`execute`. And suggests using the methods from `FinderMethods`. These
will perform the correct authorization checks on the resource when it
is found.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fix N+1 queries in uploads check rake task
Closes #47924
See merge request gitlab-org/gitlab-ce!20012
|
| | |_|_|/
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fall back to the first sign-in tab if the local storage value is bad
See merge request gitlab-org/gitlab-ce!20050
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If `current_signin_tab` is `#crowd`, then no tab will be active. Fix
this by using the first available tab.
Relates to https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20049#note_82996324
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
'master'
Notify only merge request unmergeable due to conflict
See merge request gitlab-org/gitlab-ce!19548
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There is still the edge case when 'no commits' changes to 'conflict'
would not trigger notification, which we ignore for now.
Calling can_be_merged? can cause exception (e.g. non-UTF8)
Ignore those by rescueing.
Remove unmergeable_reason as now only conflict is notified
Update spec
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Make the stubbed methods for SAML authorize paths more specific
See merge request gitlab-org/gitlab-ce!20009
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Globally stubbing any instance of `Object` seems like a very bad idea,
and it led to test failures here:
- https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/76025159
- https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/76024972
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Limit the action suffixes in transaction metrics
See merge request gitlab-org/gitlab-ce!20032
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
There seem to be a lot of cases where the suffix of an action (e.g.
".html") is set to bogus data, such as "*/*" or entire URLs. This can
increase cardinality of our metrics, and isn't very useful for
monitoring and filtering. To work around this, we enforce a whitelist
containing a few suffixes we actually care about. Suffixes not supported
will be grouped under the action without a suffix. This means that a
request to "FooController#bar.jpeg" will be assigned to
"FooController#bar".
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Remove remaining traces of the Allocations Gem
See merge request gitlab-org/gitlab-ce!20029
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In MR https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15834 we
removed use of the data produced by the Allocations Gem. However, we
never removed the code that just enables tracking of allocations. In
this commit we remove all remaining traces of this Gem.
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
Use eslint to find unused directives
See merge request gitlab-org/gitlab-ce!19940
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Move mergablility check to Gitaly
Closes gitaly#889
See merge request gitlab-org/gitlab-ce!20019
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Closes https://gitlab.com/gitlab-org/gitaly/issues/889
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
with CORS
|
|\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
'47631-operations-kubernetes-option-is-always-visible-when-repository-or-builds-are-disabled' into 'master'
Operations and Kubernetes option should be omitted when repository or builds are disabled
Closes #47631
See merge request gitlab-org/gitlab-ce!19835
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
repository or builds are disabled
|
| |_|/ / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
incompatible with Tiller v2.7.0'"
|
|\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Resolve "Set the language setting to something other than English, the branch of Merge Request will not be visible."
Closes #48100
See merge request gitlab-org/gitlab-ce!20016
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Rails5 fix expected: 1 time with arguments: (97, anything, {"squash"=>false}) received: 0 times
Closes #48104
See merge request gitlab-org/gitlab-ce!20004
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
{"squash"=>false}) received: 0 times
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Rails5 fix Projects::PagesController spec
See merge request gitlab-org/gitlab-ce!20007
|
| | |/ / / / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Implement filtering by filename on code search
Closes #43627
See merge request gitlab-org/gitlab-ce!19509
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
LFS changes are detected by Gitaly
Closes gitaly#935
See merge request gitlab-org/gitlab-ce!19995
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Closes https://gitlab.com/gitlab-org/gitaly/issues/935
|
| |_|/ / / / /
|/| | | | | | |
|
| |_|/ / / /
|/| | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Expose whether current user can push into a branch on branches API
See merge request gitlab-org/gitlab-ce!19958
|
| | |_|_|_|/
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix flakey time-senstive group filter specs
See merge request gitlab-org/gitlab-ce!19880
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This passed previously because the filtered group search is debounced by 0.5s. The test cleared the input, entered `group1`, cleared the input, entered nothing, and the all of groups are still listed because of the 0.5s debounce hasn't triggered and the test passes before anything is actually filtered.
Even if we assert that the list is filtered before clearing the input, the test still fails because the nature of the `fill_in 'filter', with: ""` method is that ["if you're setting the value to "", no keys are ever actually sent, hence no [`input`] event"](https://github.com/teamcapybara/capybara/issues/203#issuecomment-557281) and we never filter back to everything in the list.
So the solution is two-fold, add in the assertions that the list is actually filtered after each step. Then use a method that fills the input with proper events fired.
|