dadc531353
By default instrumentation will instrument public, protected and private methods, because usually heavy work is done on private method or at least that’s what facts is showing |
||
---|---|---|
.. | ||
architecture.md | ||
ci_setup.md | ||
code_review.md | ||
db_dump.md | ||
doc_styleguide.md | ||
gitlab_diagram_overview.odg | ||
gitlab_diagram_overview.png | ||
gotchas.md | ||
instrumentation.md | ||
licensing.md | ||
migration_style_guide.md | ||
omnibus.md | ||
performance.md | ||
profiling.md | ||
rake_tasks.md | ||
README.md | ||
scss_styleguide.md | ||
shared_files.md | ||
shell_commands.md | ||
sidekiq_debugging.md | ||
sql.md | ||
testing.md | ||
ui_guide.md |
Development
- Architecture of GitLab
- CI setup for testing GitLab
- Code review guidelines for reviewing code and having code reviewed.
- Gotchas to avoid
- How to dump production data to staging
- Instrumentation
- Licensing for ensuring license compliance
- Migration Style Guide for creating safe migrations
- Performance guidelines
- Rake tasks for development
- Shell commands in the GitLab codebase
- Sidekiq debugging
- SQL guidelines for SQL guidelines
- Testing standards and style guidelines
- UI guide for building GitLab with existing css styles and elements