| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Using correct column for sorting users by Recent Sign-in
Closes #26468
See merge request gitlab-org/gitlab-ce!13852
|
| | |
| |
| |
| | |
Removing last_sign_in_at in specs
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Add missing foreign key and NOT NULL constraints to todos table.
Closes #32282
See merge request gitlab-org/gitlab-ce!16849
|
| | | |
|
| | |
| |
| |
| | |
Fixes #32282.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Encode GitalyClient::WikiPage attributes to UTF-8
See merge request gitlab-org/gitlab-ce!16925
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Store uploader context in uploads
Closes #42547
See merge request gitlab-org/gitlab-ce!16779
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add backend for persistently dismissible callouts
See merge request gitlab-org/gitlab-ce!16735
|
| | | | | |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |_|_|/
|/| | |
| | | |
| | | | |
namespace
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Client changes for Tag,BranchNamesContainingCommit
See merge request gitlab-org/gitlab-ce!16789
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As part of gitlab-org/gitaly#884, this commit contains the client
implementation for both TagNamesContaintingCommit and
BranchNamesContainingCommit. The interface in the Repository model stays
the same, but the implementation on the serverside, e.g. Gitaly, uses
`for-each-ref`, as opposed to `branch` or `tag` which both aren't
plumbing command. The result stays the same.
On the serverside, we have the opportunity to limit the number of names
to return. However, this is not supported on the front end yet. My
proposal to use this ability: gitlab-org/gitlab-ce#42581. For now, this
ability is not used as that would change more behaviours on a feature
flag which might lead to unexpected changes on page refresh for example.
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
'fix/remove-duplicated-logic-between-model-and-lib-in-find-branch' into 'master'
Remove repo reloading logic from Repository#find_branch
Closes #42609
See merge request gitlab-org/gitlab-ce!16815
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Gitlab::Git::Repository#find_branch has a similar logic.
Fixes #42609
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
into 'master'
Sanitize extra blank spaces used when uploading a SSH key
Closes #40552
See merge request gitlab-org/gitlab-ce!16821
|
| | | | | | | |
|
| | |_|_|_|/
|/| | | |
| | | | |
| | | | | |
including/extending it
|
| | |_|/ /
|/| | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Enable Style/RegexpLiteral cop
Closes #42497
See merge request gitlab-org/gitlab-ce!16752
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Stop rescuing Rugged::Reference in Repository cache
See merge request gitlab-org/gitlab-ce!16770
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Migrate fetching wiki page formatted content to Gitaly
Closes gitaly#958
See merge request gitlab-org/gitlab-ce!16716
|
| | | |/
| |/|
| | |
| | | |
Closes gitaly#958
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
'42160-error-500-loading-merge-request-undefined-method-index-for-nil-nilclass' into 'master'
Resolve "Error 500 loading merge request: undefined method `index' for nil:NilClass"
Closes #42160
See merge request gitlab-org/gitlab-ce!16795
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
It appears that some legacy diff notes on GitLab.com have invalid line codes,
which means truncated_diff_lines won't work. This is just a band-aid solution,
as neither the diff nor the discussion will display correctly for these notes,
but they won't cause a 500 error.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Check MR state before submitting queries for discussion state
Closes #42236
See merge request gitlab-org/gitlab-ce!16788
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
Leaving a trailing slash in the context option causes the jira-ruby
gem to add an extra slash in HTTP requests to the URL, preventing
JIRA from working properly.
Closes #42494
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix cache clear windows
Closes #42487
See merge request gitlab-org/gitlab-ce!16740
|
| | |/ |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Add a lint check to restrict use of Rugged
See merge request gitlab-org/gitlab-ce!16656
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Look at system notes created just before merge as well as after, when deciding if an MR can be reverted
Closes #42377
See merge request gitlab-org/gitlab-ce!16678
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On MySQL, at least, `Note#created_at` doesn't seem to store fractional seconds,
while `MergeRequest::Metrics#merged_at` does. This breaks the optimization
assumption that we only need to search for notes created *after* the MR has
been merged.
Unsynchronized system clocks also make this a dangerous assumption to make.
Adding a minute of leeway still optimizes away most notes, but allows both
cases to be handled more gracefully. If the system clocks are more than a
minute out, we'll still be broken, of course.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Add formatted_data attribute to Git::WikiPage
Closes #39805
See merge request gitlab-org/gitlab-ce!16682
|
| | |/
| |
| |
| | |
Related to #39805
|
