An error occurred fetching the project authors.
- 24 Jul, 2015 3 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
I hope this makes the backup tests more reliable.
-
- 10 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 09 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 08 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 07 Jul, 2015 1 commit
-
-
Jacob Vosmaer authored
-
- 06 Jul, 2015 11 commits
-
-
Jacob Vosmaer authored
This change helps system administrators who want to replicate GitLab backup files without needing root permissions.
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Use teaspoon instead of jasmine:ci
-
Dmitriy Zaporozhets authored
Disable sticky diffs Revert feature introduced in https://github.com/gitlabhq/gitlabhq/pull/8760 Why? * It has unfixed bug for long time which is really annoying - https://github.com/gitlabhq/gitlabhq/pull/8760 * I was not able to properly fix it * It affected performance in bad way See merge request !935
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Audit log for user authentication https://dev.gitlab.org/gitlab/gitlabhq/issues/2318 See merge request !931
-
Valery Sizov authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
This reverts commit af44c650.
-
Dmitriy Zaporozhets authored
Add Irker service configuration options ### What does this MR do? This MR makes a number of hard-coded Irker parameters configurable in the service settings: Irker server host, port, and default IRC URI. It also removes the "max recipient" limit since the recipient list is configurable only by the project owner, and it makes no sense to update the limit when it is implied in the recipient list already. ### Why was this MR needed? The existing service assumed that gitlab.com was running an Irker daemon on `localhost` when it was not. Using Irker on gitlab.com thus did not work at all. This MR allows users to provide their own Irker daemons. ### Are there points in the code the reviewer needs to double check? My main concern is whether allowing a user to specify the server/port combination would have security implications for a host. Given that HipChat and Slack allow users to do this, I didn't think this was doing anything novel. ### What are the relevant issue numbers? * Closes #1713 * Closes #1714 * Closes gitlab-com/support-forum#139 ### Screenshots ### Before ![image](https://gitlab.com/stanhu/gitlab-ce/uploads/2eb3eb815e249e9fb669fc97ecd4f3c8/image.png) ### After ![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/cceaba951c05bd3df2c842cc68046b87/image.png) See merge request !930
-
Job van der Voort authored
fixed link to gitlab-basics Fixed link to gitlab-basics See merge request !1887
-
- 05 Jul, 2015 3 commits
-
-
Robert Speicher authored
Improve documentation of lists in Markdown See merge request !899
-
karen Carias authored
-
Stan Hu authored
Closes #1713 Closes #1714 Closes gitlab-com/support-forum#139
-
- 03 Jul, 2015 9 commits
-
-
Raniere Silva authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Stan Hu authored
Allow user to be blocked and activated via the API When authenticating against LDAP if a user has been disabled in LDAP they can no longer log on to the website or commit over http(s) but will be able to commit using any ssh keys. This functionality allows us to look for users in GitLab that no longer exist in LDAP and disable then in GitLab. Closes Feedback item: [Add administrative API call to block users](http://feedback.gitlab.com/forums/176466-general/suggestions/4098632-add-administrative-api-call-to-block-users) See merge request !587
-
Steve Norman authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Sytse Sijbrandij authored
Changed the reference from gitlab cloud to gitlab.com because it was outdated. This one confused me a bit because i was searching for gitlab cloud and the first thing i saw: "It's gone and now it's gitlab.com" So to prevent anyone other than me from being a bit puzzled this little change should help See merge request !929
-
Markus Mauksch authored
-
Robert Speicher authored
Fix redirection to home page URL for unauthorized users Redirection to the home page URL was broken by changing the target for `root_url` from `DashboardController` to `RootController` in 94d3c143. This regression was introduced in the 7.12.0 release. Fixes #1916. See merge request !928
-
- 02 Jul, 2015 10 commits
-
-
Daniel Gerhardt authored
Redirection to the home page URL was broken by changing the target for `root_url` from `DashboardController` to `RootController` in 94d3c143. This regression was introduced in the 7.12.0 release. Fixes #1916.
-
Job van der Voort authored
Change RC/final package release timing Creating the packages one day before the release feels strange, especially in a month like this (June 2015) where the release is on a Monday. I think it is better to have one more RC. See merge request !1873
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Add support for unlocking users in admin settings ### What does this MR do? This MR gives the ability to unlock a user from the Admin panel. ### Why was this MR needed? If a user fails to login a certain number of times, Devise locks the user out for a certain amount of time (e.g. 10 minutes). There is no way for an admin to unlock a user if this happens (aside from editing the `locked_at` field entirely). ### Screenshots #### Admin index page ![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/14c661d1d1f026770997b19af714c514/image.png) #### Admin edit user page ![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/0c6f795757e5f03eeb923d818b7d6a96/image.png) ### What are the relevant issue numbers? This replaces !288. Closes https://github.com/gitlabhq/gitlabhq/issues/9381 See merge request !922
-
Hannes Rosenögger authored
'created_at DESC' is performed twice If you are already sorting in descending order in the created_at, it is run twice when you run the .recent. It has passed in the string 'created_at DESC'. Ruby on Rails is directly given to the SQL. It is a slow query in MySQL. See merge request !825
-
catatsuy authored
-
catatsuy authored
If you are already sorting in descending order in the created_at, it is run twice when you run the .recent. It has passed in the string 'created_at DESC'. Ruby on Rails is directly given to the SQL. It is a slow query in MySQL.
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/9381
-
Dmitriy Zaporozhets authored
Correctly show anonymous authorized applications under Profile > Applications. Fixes #1907. Access tokens that were created using the ["Resource Owner Password Credentials" flow](http://doc.gitlab.com/ce/api/oauth2.html#resource-owner-password-credentials) by the user entering their username and password don't have a connected application, so the Profile > Applications page used to crash. These tokens are now rendered as "Anonymous" and can be revoked. ![Screen_Shot_2015-07-02_at_11.53.55](https://gitlab.com/gitlab-org/gitlab-ce/uploads/0fb044ce1fbf5d5e2825c3abee7763ee/Screen_Shot_2015-07-02_at_11.53.55.png) See merge request !924
-
Douwe Maan authored
-