Commit 0117de31 authored by Alex Ives's avatar Alex Ives

Update a few of the database dictionary docs

A few of the database dictionary docs didn't match the spreadsheet
that was put together to identify group table ownership. These
tables should now be owned by the correct groups.

Relates to https://gitlab.com/gitlab-org/database-team/team-tasks/-/issues/183
parent 043a8f97
......@@ -2,5 +2,5 @@
table_name: approval_merge_request_rules_approved_approvers
classes: []
feature_categories:
- source_code_management
- code_review
description:
......@@ -3,5 +3,5 @@ table_name: boards
classes:
- Board
feature_categories:
- team_planning
- design_management
description:
......@@ -3,5 +3,5 @@ table_name: ci_build_report_results
classes:
- Ci::BuildReportResult
feature_categories:
- continuous_integration
- code_testing
description:
......@@ -3,5 +3,5 @@ table_name: ci_pipelines
classes:
- Ci::Pipeline
feature_categories:
- code_review
- continuous_integration
description:
......@@ -3,5 +3,5 @@ table_name: ci_pipelines_config
classes:
- Ci::PipelineConfig
feature_categories:
- pipeline_authoring
- continuous_integration
description:
......@@ -3,5 +3,5 @@ table_name: ci_runner_namespaces
classes:
- Ci::RunnerNamespace
feature_categories:
- continuous_integration
- runner
description:
......@@ -3,5 +3,5 @@ table_name: ci_unit_test_failures
classes:
- Ci::UnitTestFailure
feature_categories:
- continuous_integration
- code_testing
description:
......@@ -3,5 +3,5 @@ table_name: deployment_merge_requests
classes:
- DeploymentMergeRequest
feature_categories:
- deployment_management
- advanced_deployments
description:
......@@ -3,5 +3,5 @@ table_name: description_versions
classes:
- DescriptionVersion
feature_categories:
- team_planning
- design_management
description:
......@@ -3,5 +3,5 @@ table_name: dora_daily_metrics
classes:
- Dora::DailyMetrics
feature_categories:
- continuous_delivery
- value_stream_management
description:
......@@ -3,5 +3,5 @@ table_name: experiment_subjects
classes:
- ExperimentSubject
feature_categories:
- experimentation_expansion
- experimentation_conversion
description:
......@@ -3,5 +3,5 @@ table_name: experiment_users
classes:
- ExperimentUser
feature_categories:
- experimentation_expansion
- experimentation_conversion
description:
......@@ -3,5 +3,5 @@ table_name: fork_network_members
classes:
- ForkNetworkMember
feature_categories:
- devops_reports
- source_code_management
description:
......@@ -3,5 +3,5 @@ table_name: in_product_marketing_emails
classes:
- Users::InProductMarketingEmail
feature_categories:
- navigation
- experimentation_activation
description:
......@@ -3,5 +3,5 @@ table_name: issue_email_participants
classes:
- IssueEmailParticipant
feature_categories:
- users
- service_desk
description:
......@@ -3,5 +3,5 @@ table_name: issue_metrics
classes:
- Issue::Metrics
feature_categories:
- source_code_management
- value_stream_management
description:
......@@ -3,6 +3,5 @@ table_name: issue_user_mentions
classes:
- IssueUserMention
feature_categories:
- users
- team_planning
description:
......@@ -4,4 +4,5 @@ classes:
- LfsObjectsProject
feature_categories:
- git_lfs
- source_code_management
description:
......@@ -3,5 +3,5 @@ table_name: lists
classes:
- List
feature_categories:
- team_planning
- design_management
description:
......@@ -6,5 +6,6 @@ classes:
- ProjectMember
- ProjectNamespaceMember
feature_categories:
- authentication_and_authorization
- projects
- subgroups
description:
......@@ -3,5 +3,5 @@ table_name: merge_request_assignees
classes:
- MergeRequestAssignee
feature_categories:
- team_planning
- code_review
description:
......@@ -3,5 +3,6 @@ table_name: merge_request_metrics
classes:
- MergeRequest::Metrics
feature_categories:
- metrics
- value_stream_management
- code_review
description:
......@@ -4,5 +4,4 @@ classes:
- MergeRequestUserMention
feature_categories:
- code_review
- users
description:
......@@ -3,5 +3,5 @@ table_name: merge_requests_closing_issues
classes:
- MergeRequestsClosingIssues
feature_categories:
- team_planning
- code_review
description:
......@@ -3,5 +3,5 @@ table_name: namespace_root_storage_statistics
classes:
- Namespace::RootStorageStatistics
feature_categories:
- subgroups
- utilization
description:
......@@ -3,5 +3,5 @@ table_name: namespace_statistics
classes:
- NamespaceStatistics
feature_categories:
- source_code_management
- utilization
description:
......@@ -3,5 +3,5 @@ table_name: notification_settings
classes:
- NotificationSetting
feature_categories:
- users
- team_planning
description:
......@@ -3,5 +3,5 @@ table_name: project_authorizations
classes:
- ProjectAuthorization
feature_categories:
- authentication_and_authorization
- projects
description:
......@@ -3,5 +3,5 @@ table_name: project_auto_devops
classes:
- ProjectAutoDevops
feature_categories:
- continuous_integration
- auto_devops
description:
......@@ -3,5 +3,5 @@ table_name: project_repositories
classes:
- ProjectRepository
feature_categories:
- projects
- source_code_management
description:
......@@ -3,5 +3,5 @@ table_name: project_repository_states
classes:
- ProjectRepositoryState
feature_categories:
- projects
- source_code_management
description:
......@@ -3,5 +3,5 @@ table_name: project_repository_storage_moves
classes:
- Projects::RepositoryStorageMove
feature_categories:
- gitaly
- source_code_management
description:
......@@ -3,5 +3,5 @@ table_name: project_settings
classes:
- ProjectSetting
feature_categories:
- error_tracking
- projects
description:
......@@ -3,5 +3,5 @@ table_name: push_event_payloads
classes:
- PushEventPayload
feature_categories:
- gitaly
- source_code_management
description:
......@@ -3,5 +3,5 @@ table_name: push_rules
classes:
- PushRule
feature_categories:
- source_code_management
- compliance_management
description:
......@@ -3,5 +3,5 @@ table_name: resource_iteration_events
classes:
- ResourceIterationEvent
feature_categories:
- users
- planning_analytics
description:
......@@ -3,6 +3,5 @@ table_name: resource_label_events
classes:
- ResourceLabelEvent
feature_categories:
- projects
- subgroups
- planning_analytics
description:
......@@ -2,7 +2,6 @@
table_name: resource_state_events
classes:
- ResourceStateEvent
feature_categories:
- source_code_management
feature_categories:
- team_planning
description:
......@@ -3,5 +3,5 @@ table_name: timelogs
classes:
- Timelog
feature_categories:
- audit_events
- team_planning
description:
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment