| Age | Commit message (Collapse) | Author |
|---|
|
project that has MRs disabled but issues enabled
Closes #1813
|
|
Fix behavior of ldap_person method in Gitlab::OAuth::User
Code tweaks in 45e9150a caused the ldap_person method to not return expected results.
Improved tests to cover the ldap_person method, which was previously stubbed.
Restored the previous implementation of ldap_person, as I could not find a more concise to write it that still works with all the test cases.
See merge request !837
|
|
|
|
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
This controller is now the target for `root_url`. It sub-classes
DashboardController so we can render the old default without a redirect
if the user hasn't customized their dashboard location.
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
cherry-picked
|
|
Look for .gitlab-ci.yml only if checkout_sha is present
Fixes https://dev.gitlab.org/gitlab/gitlabhq/issues/2396
cc @vsizov
See merge request !818
|
|
|
|
This might see a minor speedup in test cases that call this method many
times.
|
|
|
|
|
|
|
|
Fixes #1778
|
|
|
|
Order commit comments in API chronologically
When fetching commit comments via API, the comments were not ordered,
but just returned in the order Postgresql finds them. Now the API always
returns comments in chronological order.
Same as !628 but with CI
See merge request !768
|
|
Remove Guard
None of the GitLab B.V. developers were using it.
See internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2360
See merge request !764
|
|
Fix upgrader script
This is a fix for upgrader script not guessing the latest version correctly.
Upgrader now handles versions where a version part (major/minor/patch) can have multi-digit number, also ensures that the latest version is chosen from git tags by converting tag to Gitlab::VersionInfo and than selecting the latest/greatest version.
Fixes: #1476
See merge request !695
|
|
Make namespace API available to all users
### What does this MR do?
This MR makes it possible for a user to query namespaces to which he/she has access. Also, it adds documentation for the existing API.
### Why was this MR needed?
Even though the `groups` API exists, it might still be useful to have an endpoint that tells the namespace type (e.g. `user` vs. `group`), especially if a user has access to a number of different projects.
### What are the relevant issue numbers?
Closes https://github.com/gitlabhq/gitlabhq/issues/9328
See merge request !708
|
|
|
|
|
|
Group improvements
* remove projects before removing group
* execute all hooks/events from project destroy when group removed
* log group create/remove
* delay remove of namespace directory (to prevent NFS issues)
Inspired by !759
See merge request !761
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
spec/features/projects_spec.rb
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Conflicts:
spec/features/projects_spec.rb
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
Until now, a user needed to first sign in with his LDAP identity and then manually
link his/her account with an omniauth identity from their profile.
Only when this is done can the user authenticate with the omniauth provider and at
the same time benefit from the LDAP integration (HTTPS authentication with LDAP
username/password and in EE: LDAP groups, SSH keys etc.).
This feature automates the process by looking up a corresponding LDAP person when a
user connects with omniauth for the first time and then automatically linking the LDAP
and omniauth identities (of course, like the existing allow_single_sign_on setting,
this is meant to be used with trusted omniauth providers).
The result is identical to a manual account link.
Add config initializers for other omniauth settings.
|
|
|
|
Removes redundant enableButton/disableButton extensions, and adds specs
for the jQuery extensions.
|
|
|
|
Don't notify users mentioned in code blocks or blockquotes.
cc @rspeicher
See merge request !753
|
|
|
|
And make it more generalized for all filter specs.
|
|
|
|
When this option is `:description`, we use a more restrictive whitelist.
This is used for Project and Group description fields.
|
|
|
|
|
|
|
|
|
|
Create and edit files in web editor via rugged
- [x] create file via rugged
- [x] update file via rugged
- [x] remove file via rugged
- [ ] fix tests
- [x] remove satellites code
- [x] create activity event for new/edit file via rugged
- [x] base64 support
Part of https://dev.gitlab.org/gitlab/gitlabhq/issues/2300
See merge request !751
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
Fix link_to_gfm with only a reference having the incorrect link
Before:
```ruby
link_to_gfm("#4", "/foo") # => "<a href="/namespace/project/issues/4" class="gfm gfm-issue">#4</a>"
link_to_gfm("See #4", "/foo") # => "<a href="/foo">See </a><a href="/namespace/project/issues/4" class="gfm gfm-issue">#4</a>"
```
After:
```ruby
link_to_gfm("#4", "/foo") # => "<a href="/foo">#4</a>"
link_to_gfm("See #4", "/foo") # => "<a href="/foo">See </a><a href="/namespace/project/issues/4" class="gfm gfm-issue">#4</a>"
```
Closes #192
Closes #1721
Closes [GitHub #7115](https://github.com/gitlabhq/gitlabhq/issues/7115)
See merge request !739
|
