- 02 5月, 2018 1 次提交
-
-
由 Kamil Trzciński 提交于
-
- 01 5月, 2018 3 次提交
-
-
由 Filipa Lacerda 提交于
-
由 Phil Hughes 提交于
Sanitize user name to avoid XSS attacks See merge request gitlab/gitlabhq!2373
-
由 Douwe Maan 提交于
Serve archive requests with the correct file in all cases (10.7) See merge request gitlab/gitlabhq!2376
-
- 30 4月, 2018 2 次提交
-
-
由 Bob Van Landuyt 提交于
Since we only need the `can?` view helpers there, it's better to include those in a separate controller. If we inherit from `ApplicationController` we also need to deal with authentication, that needs to be done in some, but not all doorkeeper controllers.
-
由 Tiago Botelho 提交于
-
- 28 4月, 2018 1 次提交
-
-
由 Nick Thomas 提交于
-
- 27 4月, 2018 6 次提交
-
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
由 James Ramsay 提交于
To find the pipeline for a specific sha requires scanning the list of all pipelines for a ref that contains the sha. This makes it hard to find the pipeline id needed to access a trace for a specific job run in the pipeline using the API.
-
由 Winnie Hellmann 提交于
-
由 Winnie Hellmann 提交于
-
由 Tiago Botelho 提交于
-
- 26 4月, 2018 4 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Jose 提交于
-
由 Phil Hughes 提交于
-
由 Phil Hughes 提交于
-
- 25 4月, 2018 10 次提交
-
-
由 Phil Hughes 提交于
-
由 Zeger-Jan van de Weg 提交于
Has been in opt out for 5 months, and within GitLab been in production for longer than that. No code needs to be migrated as this is implemented in GoLang over at Gitaly. Closes https://gitlab.com/gitlab-org/gitaly/issues/314
-
由 Sean McGivern 提交于
The NotificationService has to do quite a lot of work to calculate the recipients for an email. Where possible, we should try to avoid doing this in an HTTP request, because the mail are sent by Sidekiq anyway, so there's no need to schedule those emails immediately. This commit creates a generic Sidekiq worker that uses Global ID to serialise and deserialise its arguments, then forwards them to the NotificationService. The NotificationService gains an `#async` method, so you can replace: notification_service.new_issue(issue, current_user) With: notification_service.async.new_issue(issue, current_user) And have everything else work as normal, except that calculating the recipients will be done by Sidekiq, which will then schedule further Sidekiq jobs to send each email.
-
由 Zeger-Jan van de Weg 提交于
Direct disk access is done through Gitaly now, so the legacy path was deprecated. This path was used in Gitlab::Shell however. This required the refactoring in this commit. Added is the removal of direct path access on the project model, as that lookup wasn't needed anymore is most cases. Closes https://gitlab.com/gitlab-org/gitaly/issues/1111
-
由 Grzegorz Bizon 提交于
-
由 Jan Provaznik 提交于
* processes any pending records which are not migrated yet * bumps import_export version because of new commits_count attribute * removes commits_count fallback method
-
由 Winnie Hellmann 提交于
-
由 Filipa Lacerda 提交于
Cleans merge request css
-
由 Kamil Trzciński 提交于
-
由 Filipa Lacerda 提交于
-
- 24 4月, 2018 9 次提交
-
-
由 Sean McGivern 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
Hide the push to master instructions for users that are not allowed to do that. Also hide buttons that would direct them to commit directly in master
-
由 Tomasz Maczukin 提交于
-
由 Sean McGivern 提交于
-
由 Semyon Pupkov 提交于
-
由 Oswaldo Ferreira 提交于
-
由 Micaël Bergeron 提交于
-
由 Felipe Artur 提交于
-
- 23 4月, 2018 4 次提交
-
-
由 Takuya Noguchi 提交于
-
由 Lin Jen-Shin 提交于
-
由 James Edwards-Jones 提交于
-
由 Bob Van Landuyt 提交于
When `Errno::EBUSY` is raised during restore, this could indicate that the directory being restored into is a mountpoint. In this case we explain the user how to retry the restore.
-