kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Fixed username links in the performance guide

Browse source 
These would end up being rendered as:

    <a href="...">@yorickpeterse</a>
    <a href="...">@yorickpeterse</a>

[ci skip]
This commit is contained in:
Yorick Peterse 2016-05-04 13:17:43 +02:00
parent 450ea01d31
commit 70551217a6
No known key found for this signature in database
GPG key ID: EDD30D2BEB691AC9
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/development/performance.md
View file

@ -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