- 04 Oct, 2016 1 commit
-
-
Yorick Peterse authored
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 Sep, 2016 1 commit
-
-
Rémy Coutable authored
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:
Rémy Coutable <remy@rymai.me>
-
- 22 Sep, 2016 3 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 21 Sep, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 20 Sep, 2016 1 commit
-
-
Stan Hu authored
In https://gitlab.com/gitlab-org/gitlab-ce/builds/4218398, the build failed because the last_activity_at column was only being updated once per hour. We can fix this spec by stubbing out the throttling and adjusting the spec to test the right event timestamp.
-
- 15 Sep, 2016 1 commit
-
-
Patricio Cano authored
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
-
- 14 Sep, 2016 1 commit
-
-
ubudzisz authored
add tests with dependent destroy add tests with dependent destroy add tests add tests to projects spec update it title and remove let update it title and remove let remove changes after rebase remove changes after rebase update changelog
-
- 13 Sep, 2016 1 commit
-
-
Yorick Peterse authored
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
-
- 01 Sep, 2016 1 commit
-
-
Felipe Artur authored
-
- 26 Aug, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 25 Aug, 2016 1 commit
-
-
Hannes Rosenögger authored
This commit makes sure that the project icon is being read from the default branch instead of 'master'
-
- 20 Aug, 2016 1 commit
-
-
Douwe Maan authored
-
- 17 Aug, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 16 Aug, 2016 1 commit
-
-
Timothy Andrew authored
1. `GitPushService` was still using `{merge,push}_access_level_attributes` instead of `{merge,push}_access_levels_attributes`. 2. The branches API creates access levels regardless of the state of the `developers_can_{push,merge}` parameters. This is in line with the UI, where Master access is the default for a new protected branch. 3. Use `after(:build)` to create access levels in the `protected_branches` factory, so that `factories_spec` passes. It only builds records, so we need to create access levels on `build` as well.
-
- 11 Aug, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 09 Aug, 2016 2 commits
-
-
Stan Hu authored
This is in preparation to address the DB load caused by the counting in gitlab-com/infrastructure#303.
-
tiagonbotelho authored
-
- 04 Aug, 2016 1 commit
-
-
tiagonbotelho authored
-
- 02 Aug, 2016 1 commit
-
-
tiagonbotelho authored
developer cannot push to protected branch when project is empty or he has not been granted permission to do so
-
- 29 Jul, 2016 1 commit
-
-
Timothy Andrew authored
1. Remove `Project#developers_can_push_to_protected_branch?` since it isn't used anymore. 2. Remove `Project#developers_can_merge_to_protected_branch?` since it isn't used anymore.
-
- 27 Jul, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 26 Jul, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 21 Jul, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 20 Jul, 2016 11 commits
-
-
Alejandro Rodríguez authored
Currently, even when searching for all authorized issues of *one* project, we run the `Users#authorized_projects` query (which can be rather slow). This update checks if we are handling issues of just one project and does the authorization check locally. It does have the downside of basically repeating the logic of `Users#authorized_projects` on `Project#authorized_for_user`.
-
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
So we no longer join anything, just find the latest pipeline and load builds from there to avoid mixing builds. Thanks Kamil for the help and tests.
-
-
Lin Jen-Shin authored
this should properly test that it's really getting the builds from the latest successful pipelines and latest successful builds.
-
- 19 Jul, 2016 2 commits
-
-
Eugene Howe authored
* This method previously iterated over all services in a project. Now it will directly query the ExternalWikiService for the project and filter by active state. * The presence of an external wiki is also cached * When an external wiki is added or removed, the cached value is updated