- 25 6月, 2015 1 次提交
-
-
由 Robert Speicher 提交于
-
- 24 6月, 2015 3 次提交
-
-
由 Adam Meily 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Stan Hu 提交于
Closes https://github.com/gitlabhq/gitlabhq/issues/9391
-
- 23 6月, 2015 4 次提交
-
-
由 Stan Hu 提交于
Closes #1225 Closes #1854 Closes #1858
-
由 Valery Sizov 提交于
-
由 Stan Hu 提交于
Closes #1856 Closes https://github.com/gitlabhq/gitlabhq/issues/9394
-
由 Rowan Wookey 提交于
-
- 22 6月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Valery Sizov 提交于
-
- 20 6月, 2015 4 次提交
-
-
由 Douwe Maan 提交于
-
由 Stan Hu 提交于
Closes #1815
-
由 Stan Hu 提交于
Disable changing of target branch in new merge request page when a branch has already been specified Closes #1830
-
由 Robert Speicher 提交于
-
- 19 6月, 2015 4 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Replaced: * "Accepted" with "Merged" * "Rejected" with "Closed" Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Stan Hu 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 16 6月, 2015 1 次提交
-
-
由 Stan Hu 提交于
Closes https://github.com/gitlabhq/gitlabhq/issues/9283
-
- 15 6月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Marin Jankovski 提交于
-
- 14 6月, 2015 2 次提交
-
-
由 Daniel Gerhardt 提交于
The creation of cross references for external issues (which would fail) is now prevented. Fixes #1650, GH-9333.
-
由 Robert Speicher 提交于
-
- 13 6月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 6月, 2015 1 次提交
-
-
由 Stan Hu 提交于
Closes #1700 Closes #1720
-
- 11 6月, 2015 1 次提交
-
-
由 Max Borghino 提交于
Both new buttons are 64x64 renders of the recommended assets from each company. Refs for those are: - https://about.twitter.com/press/twitter-brand-policy - https://developers.google.com/identity/branding-guidelines Addresses issue #544
-
- 10 6月, 2015 1 次提交
-
-
由 Stan Hu 提交于
Closes #1775
-
- 05 6月, 2015 5 次提交
-
-
由 Eric Maziade 提交于
settings
-
由 Daniel Gerhardt 提交于
If HTTPS was used for 'project_url', an error was raised because a HTTP connection was established to the default HTTPS port. The code has been corrected and simplified by using HTTParty. Additionally, the request now is made directly to the 'project_url' instead of the extracted root path.
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 03 6月, 2015 6 次提交
-
-
由 Marin Jankovski 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Ths commit does next: * When we remove project we move repository to path+deleted.git * Then we schedule removal of path+deleted with sidekiq * If repository move failed we abort project removal This should help us with NFS issue when project get removed but repository stayed. The full explanation of problem is below: * rm -rf project.git * rm -rf removes project.git/objects/foo * NFS server renames foo to foo.nfsXXXX because some NFS client (think * Unicorn) still has the file open * rm -rf exits, but project.git/objects/foo.nfsXXX still exists * Unicorn closes the file, the NFS client closes the file (foo), and the * NFS server removes foo.nfsXXX * the directory project.git/objects/ still exists => problem So now we move repository and even if repository removal failed Repository directory is moved so no bugs with project removed but repository directory taken. User still able to create new project with same name. From administrator perspective you can easily find stalled repositories by searching `*+deleted.git` Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Alex Lossent 提交于
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.
-
-
由 Toni Lähdekorpi 提交于
-
- 02 6月, 2015 2 次提交
-
-
由 Valery Sizov 提交于
-
由 Douwe Maan 提交于
-