diff options
| author | Alejandro RodrÃguez <alejorro70@gmail.com> | 2018-10-02 00:21:46 -0300 |
|---|---|---|
| committer | Alejandro RodrÃguez <alejorro70@gmail.com> | 2018-10-02 16:34:28 -0300 |
| commit | a99bf447a24957cf11b89d4f04a2b84613367ef2 (patch) | |
| tree | 68821625f3e39e81f495d89537b55334180b0f77 /doc/development/instrumentation.md | |
| parent | 0ef1060e14b8ac09159e466fe5f4ca3195e080c2 (diff) | |
| download | gitlab-ce-a99bf447a24957cf11b89d4f04a2b84613367ef2.tar.gz | |
Remove Gitlab::Git::Repository#rugged and Gollum code
Cleanup code, and refactor tests that still use Rugged. After this, there should
be no Rugged code that access the instance's repositories on non-test
environments. There is still some rugged code for other tasks like the
repository import task, but since it doesn't access any repository storage path
it can stay.
Diffstat (limited to 'doc/development/instrumentation.md')
| -rw-r--r-- | doc/development/instrumentation.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/instrumentation.md b/doc/development/instrumentation.md index a14c0752366..7761f65d78a 100644 --- a/doc/development/instrumentation.md +++ b/doc/development/instrumentation.md @@ -69,7 +69,7 @@ The easiest way to check if a method has been instrumented is to check its source location. For example: ```ruby -method = Rugged::TagCollection.instance_method(:[]) +method = Banzai::Renderer.method(:render) method.source_location ``` @@ -82,7 +82,7 @@ method (along with its source location), this is easier than running the above Ruby code. In case of the above snippet you'd run the following: ``` -$ Rugged::TagCollection#[] +$ Banzai::Renderer.render ``` This will print out something along the lines of: |