| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is overdue, and some of the suggestions are embarrassing, but
this is how we actually develop Danger today.
|
|
Explain Workhorse acceleration features
|
|
Includes a new database case study about all the approaches taken to
store and update the namespace statistics in a performan manner
performant approach to store and update the namespaces statistics
|
|
Deletes extra spaces and line, makes lists consistent, and
fixes links.
|
|
|
|
|
|
Add development documentation on label filtering
Closes #49651
See merge request gitlab-org/gitlab-ce!30741
|
|
This topic comes up periodically, and we've investigated several options
for changing the way we filter labels. Unfortunately, we have yet to
find an option that is strictly better than the current state.
|
|
See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069
|
|
It's not uncommon that a single code change can reflect and
interact with multiple parts of GitLab codebase, making it
possible to break an existing feature.
This commit expands documentation in that regard for developers.
|
|
|
