From 22cfb8588ce0752c11397eae158a935709fe533d Mon Sep 17 00:00:00 2001 From: Stan Hu Date: Sun, 23 Jun 2019 23:48:52 -0700 Subject: Remove requirement for personal access token in profiling Since https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23320, personal access tokens are no longer needed for profiling an endpoint since users are stubbed directly. --- doc/development/profiling.md | 4 ---- 1 file changed, 4 deletions(-) (limited to 'doc/development/profiling.md') diff --git a/doc/development/profiling.md b/doc/development/profiling.md index b2f3a105b23..795523b82aa 100644 --- a/doc/development/profiling.md +++ b/doc/development/profiling.md @@ -38,10 +38,6 @@ For routes that require authorization you will need to provide a user to Gitlab::Profiler.profile('/gitlab-org/gitlab-test', user: User.first) ``` -The user you provide will need to have a [personal access -token](https://docs.gitlab.com/ce/user/profile/personal_access_tokens.html) in -the GitLab instance. - Passing a `logger:` keyword argument to `Gitlab::Profiler.profile` will send ActiveRecord and ActionController log output to that logger. Further options are documented with the method source. -- cgit v1.2.3