diff options
| author | Yorick Peterse <yorickpeterse@gmail.com> | 2016-05-04 13:17:43 +0200 |
|---|---|---|
| committer | Yorick Peterse <yorickpeterse@gmail.com> | 2016-05-04 13:17:43 +0200 |
| commit | 70551217a6cc250dc2e9a61720fc447df74e38c7 (patch) | |
| tree | e184c6c55652229a8f714392df5982fa42a39bfd | |
| parent | 450ea01d31fb1799de795efc94c3da9395cd9fa7 (diff) | |
| download | gitlab-ce-70551217a6cc250dc2e9a61720fc447df74e38c7.tar.gz | |
Fixed username links in the performance guide
These would end up being rendered as:
<a href="...">@yorickpeterse</a>
<a href="...">@yorickpeterse</a>
[ci skip]
| -rw-r--r-- | doc/development/performance.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/performance.md b/doc/development/performance.md index 41f415812a0..fb37b3a889c 100644 --- a/doc/development/performance.md +++ b/doc/development/performance.md @@ -16,7 +16,7 @@ The process of solving performance problems is roughly as follows: timings, etc) to the issue mentioned in step 1. 4. Solve the problem. 5. Create a merge request, assign the "performance" label and ping the right - people (e.g. [@yorickpeterse][@yorickpeterse] and [@joshfng][@joshfng]). + people (e.g. [@yorickpeterse][yorickpeterse] and [@joshfng][joshfng]). 6. Once a change has been deployed make sure to _again_ measure for at least 24 hours to see if your changes have any impact on the production environment. 7. Repeat until you're done. @@ -253,6 +253,6 @@ impact on runtime performance, and as such, using a constant instead of referencing an object directly may even slow code down. [#15607]: https://gitlab.com/gitlab-org/gitlab-ce/issues/15607 -[@yorickpeterse]: https://gitlab.com/u/yorickpeterse -[@joshfng]: https://gitlab.com/u/joshfng +[yorickpeterse]: https://gitlab.com/u/yorickpeterse +[joshfng]: https://gitlab.com/u/joshfng [anti-pattern]: https://en.wikipedia.org/wiki/Anti-pattern |