- 01 11月, 2016 2 次提交
-
-
由 Felipe Artur 提交于
-
-
- 28 10月, 2016 1 次提交
-
-
由 Adam Niedzielski 提交于
Do not pass project.owner because it may return a group and Labels::FindOrCreateService throws an error in this case. Fixes #23694.
-
- 25 10月, 2016 1 次提交
-
-
由 David Wagner 提交于
They were Rails' default and are unnecessarily overridden. Signed-off-by: NDavid Wagner <david@marvid.fr>
-
- 21 10月, 2016 1 次提交
-
-
Callback associations are not common to see around. We want to make clear that the `before_add` callback uses the number before the addition, in this particular case 1.
-
- 20 10月, 2016 8 次提交
-
-
由 Felipe Artur 提交于
-
-
-
由 James Lopez 提交于
Fixed all related specs and also changed the logic to handle edge cases. This includes exporting and exporting of group labels, which will get associated with the new group (if any) or they will become normal project labels otherwise. Found other issues to do with not being able to import all labels at once in the beginning of the JSON - code was much simpler when we import all labels and milestones associated to a project first, then the associations will find the already created labels instead of creating them from the associations themselves.
-
-
-
-
-
- 19 10月, 2016 1 次提交
-
-
由 Felipe Artur 提交于
-
- 17 10月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 13 10月, 2016 1 次提交
-
-
由 Paco Guzman 提交于
-
- 11 10月, 2016 3 次提交
-
-
- 10 10月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This commit introduces a Sidekiq worker that precalculates the list of trending projects on a daily basis. The resulting set is stored in a database table that is then queried by Project.trending. This setup means that Unicorn workers no longer _may_ have to calculate the list of trending projects. Furthermore it supports filtering without any complex caching mechanisms. The data in the "trending_projects" table is inserted in the same order as the project ranking. This means that getting the projects in the correct order is simply a matter of: SELECT projects.* FROM projects INNER JOIN trending_projects ON trending_projects.project_id = projects.id ORDER BY trending_projects.id ASC; Such a query will only take a few milliseconds at most (as measured on GitLab.com), opposed to a few seconds for the query used for calculating the project ranks. The migration in this commit does not require downtime and takes care of populating an initial list of trending projects.
-
- 07 10月, 2016 1 次提交
-
-
由 Nick Thomas 提交于
This commit adds a number of _html columns and, with the exception of Note, starts updating them whenever the content of their partner fields changes. Note has a collision with the note_html attr_accessor; that will be fixed later A background worker for clearing these cache columns is also introduced - use `rake cache:clear` to set it off. You can clear the database or Redis caches separately by running `rake cache:clear:db` or `rake cache:clear:redis`, respectively.
-
- 06 10月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 05 10月, 2016 2 次提交
-
-
由 James Lopez 提交于
-
由 Yorick Peterse 提交于
Having many system notes isn't really an indication of a project being trending. Including these notes would lead to projects with lots of commit cross references (for example) showing up in the trending projects list.
-
- 28 9月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Changes include: - Ensure Member.add_user is not called directly when not necessary - New GroupMember.add_users_to_group to have the same abstraction level as for Project - Refactor Member.add_user to take a source instead of an array of members - Fix Rubocop offenses - Always use Project#add_user instead of project.team.add_user - Factorize users addition as members in Member.add_users_to_source - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects - Destroy any requester before adding them as a member - Improve the way we handle access requesters in Member.add_user Instead of removing the requester and creating a new member, we now simply accepts their access request. This way, they will receive a "access request granted" email. - Fix error that was previously silently ignored - Stop raising when access level is invalid in Member, let Rails validation do their work Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 22 9月, 2016 3 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 21 9月, 2016 3 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
- For target project show only environments for target branch or with tags - For source project show only environments for source branch
-
- 16 9月, 2016 2 次提交
-
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
-
- 14 9月, 2016 2 次提交
-
-
由 Yorick Peterse 提交于
This moves tracking of the pushes since the last Git GC from PostgreSQL to Redis. This reduces the number of writes on the "projects" table. This in turn reduces the vacuuming overhead. The lease used for incrementing the counter has been removed. This lease was mostly put in place to prevent high database load but this isn't needed anymore due to the counter now being stored in Redis. Fixes gitlab-org/gitlab-ce#22125
- 13 9月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
Use a permissions of user to access all dependent projects from CI jobs (this also includes a container images, and in future LFS files)
-
- 06 9月, 2016 1 次提交
-
-
由 Connor Shea 提交于
-
- 01 9月, 2016 3 次提交
-
-
由 Felipe Artur 提交于
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
-