doc/gitaly: Remove references to removed metrics
What does this MR do and why?
In Add Metrics Dashboard menu (!121742 - merged), we fixed a bug where a menu items that had been missed when migrating to the new navigation was re-added.
This MR backports that fix to v15.11
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The original MR has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:package-and-test-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Merge request reports
Activity
added backend bugfunctional devopsmanage groupfoundations sectiondev severity1 typebug labels
assigned to @joseph
mentioned in issue Taucher2003/reporting#10 (closed)
- A deleted user
added database documentation feature flag frontend labels
9 Warnings CHANGELOG.md was edited. Please remove the additions and follow the changelog guidelines. If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
This MR has a Changelog commit for EE, but no code changes in ee/
. Consider removing theEE: true
trailer from your commits.This merge request has more than 20 commits which may cause issues in some of the jobs. If you see errors like missing commits, please consider squashing some commits so it is within 20 commits. This merge request changed files with disabled eslint rules. Please consider fixing them. This merge request does not refer to an existing milestone. This merge request contains deprecated components. Please consider using Pajamas components instead. The e2e:package-and-test-ee
job needs to succeed or have approval from a Software Engineer in Test.
Read the "QA e2e:package-and-test-ee" section for more details.This merge request adds a new rule to app/assets/stylesheets/framework/common.scss or app/assets/stylesheets/utilities.scss. This merge request changed undocumented Vue components in
vue_shared/
. Please consider creating Stories for these components:app/assets/javascripts/vue_shared/components/markdown/editor_mode_switcher.vue
app/assets/javascripts/vue_shared/components/entity_select/entity_select.vue
app/assets/javascripts/vue_shared/components/file_finder/index.vue
app/assets/javascripts/vue_shared/components/filtered_search_bar/filtered_search_bar_root.vue
app/assets/javascripts/vue_shared/components/form/form_footer_actions.vue
app/assets/javascripts/vue_shared/components/markdown/comment_templates_dropdown.vue
app/assets/javascripts/vue_shared/components/markdown/drawio_toolbar_button.vue
app/assets/javascripts/vue_shared/components/markdown/field.vue
app/assets/javascripts/vue_shared/components/markdown/header.vue
app/assets/javascripts/vue_shared/components/markdown/markdown_editor.vue
app/assets/javascripts/vue_shared/components/markdown/toolbar.vue
app/assets/javascripts/vue_shared/components/markdown/toolbar_button.vue
app/assets/javascripts/vue_shared/components/notes/noteable_warning.vue
app/assets/javascripts/vue_shared/components/projects_list/projects_list.vue
app/assets/javascripts/vue_shared/components/projects_list/projects_list_item.vue
app/assets/javascripts/vue_shared/components/registry/registry_search.vue
app/assets/javascripts/vue_shared/components/runner_instructions/runner_instructions_modal.vue
app/assets/javascripts/vue_shared/components/user_avatar/user_avatar_link.vue
app/assets/javascripts/vue_shared/components/user_avatar/user_avatar_list.vue
app/assets/javascripts/vue_shared/components/diff_stats_dropdown.vue
app/assets/javascripts/vue_shared/components/dismissible_feedback_alert.vue
app/assets/javascripts/vue_shared/components/modal_copy_button.vue
app/assets/javascripts/vue_shared/components/time_ago_tooltip.vue
app/assets/javascripts/vue_shared/components/web_ide_link.vue
app/assets/javascripts/vue_shared/issuable/create/components/issuable_form.vue
app/assets/javascripts/vue_shared/issuable/create/components/issuable_label_selector.vue
app/assets/javascripts/vue_shared/issuable/list/components/issuable_item.vue
app/assets/javascripts/vue_shared/issuable/list/components/issuable_list_root.vue
app/assets/javascripts/vue_shared/new_namespace/components/welcome.vue
app/assets/javascripts/vue_shared/new_namespace/new_namespace_page.vue
app/assets/javascripts/vue_shared/security_configuration/components/manage_via_mr.vue
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
data/whats_new/202304220001_15_11.yml
(Link to current live version) -
db/docs/batched_background_migrations/backfill_design_management_repositories.yml
(Link to current live version) -
db/docs/batched_background_migrations/backfill_work_item_type_id_for_issues.yml
(Link to current live version) -
db/docs/batched_background_migrations/cleanup_personal_access_tokens_with_nil_expires_at.yml
(Link to current live version) -
db/docs/batched_background_migrations/migrate_human_user_type.yml
(Link to current live version) -
db/docs/batched_background_migrations/populate_vulnerability_dismissal_fields.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_elastic_stacks.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_integration_elasticstack.yml
(Link to current live version) -
db/docs/deleted_tables/experiment_subjects.yml
(Link to current live version) -
db/docs/deleted_tables/experiment_users.yml
(Link to current live version) -
db/docs/deleted_tables/experiments.yml
(Link to current live version) -
db/docs/deleted_tables/geo_container_repository_updated_events.yml
(Link to current live version) -
db/docs/deleted_tables/geo_job_artifact_deleted_events.yml
(Link to current live version) -
db/docs/deleted_tables/geo_lfs_object_deleted_events.yml
(Link to current live version) -
db/docs/deleted_tables/partitioned_foreign_keys.yml
(Link to current live version) -
db/docs/deleted_tables/post_migration_test_table.yml
(Link to current live version) -
db/docs/deleted_tables/project_tracing_settings.yml
(Link to current live version) -
db/docs/deleted_tables/vulnerability_finding_evidence_assets.yml
(Link to current live version) -
db/docs/deleted_tables/vulnerability_finding_evidence_headers.yml
(Link to current live version) -
db/docs/deleted_tables/vulnerability_finding_evidence_requests.yml
(Link to current live version) -
db/docs/deleted_tables/vulnerability_finding_evidence_responses.yml
(Link to current live version) -
db/docs/deleted_tables/vulnerability_finding_evidence_sources.yml
(Link to current live version) -
db/docs/deleted_tables/vulnerability_finding_evidence_supporting_messages.yml
(Link to current live version) -
db/docs/abuse_report_events.yml
(Link to current live version) -
db/docs/audit_events_google_cloud_logging_configurations.yml
(Link to current live version) -
db/docs/ci_editor_ai_conversation_messages.yml
(Link to current live version) -
db/docs/design_management_repository_states.yml
(Link to current live version) -
db/docs/merge_request_diff_llm_summaries.yml
(Link to current live version) -
db/docs/note_metadata.yml
(Link to current live version) -
db/docs/organizations.yml
(Link to current live version) -
db/docs/pm_advisories.yml
(Link to current live version) -
db/docs/pm_affected_packages.yml
(Link to current live version) -
db/docs/project_states.yml
(Link to current live version) -
db/docs/remote_development_agent_configs.yml
(Link to current live version) -
db/docs/value_stream_dashboard_aggregations.yml
(Link to current live version) -
db/docs/value_stream_dashboard_counts.yml
(Link to current live version) -
db/docs/workspaces.yml
(Link to current live version) -
db/docs/ci_minutes_additional_packs.yml
(Link to current live version) -
db/docs/events.yml
(Link to current live version) -
db/docs/historical_data.yml
(Link to current live version) -
db/docs/namespace_root_storage_statistics.yml
(Link to current live version) -
db/docs/namespace_statistics.yml
(Link to current live version) -
db/docs/resource_iteration_events.yml
(Link to current live version) -
db/docs/resource_label_events.yml
(Link to current live version) -
db/docs/resource_link_events.yml
(Link to current live version) -
db/docs/resource_milestone_events.yml
(Link to current live version) -
db/docs/resource_state_events.yml
(Link to current live version) -
db/docs/resource_weight_events.yml
(Link to current live version) -
db/docs/schema_migrations.yml
(Link to current live version) -
db/docs/verification_codes.yml
(Link to current live version) -
doc/.vale/gitlab/CIConfigFile.yml
(Link to current live version) -
doc/.vale/gitlab/ElementDescriptors.yml
(Link to current live version) -
doc/administration/auth/ldap/index.md
(Link to current live version) -
doc/administration/auth/ldap/ldap-troubleshooting.md
(Link to current live version) -
doc/administration/auth/crowd.md
(Link to current live version) -
doc/administration/auth/oidc.md
(Link to current live version) -
doc/administration/dedicated/index.md
(Link to current live version) -
doc/administration/geo/disaster_recovery/planned_failover.md
(Link to current live version) -
doc/administration/geo/replication/configuration.md
(Link to current live version) -
doc/administration/geo/replication/troubleshooting.md
(Link to current live version) -
doc/administration/geo/setup/database.md
(Link to current live version) -
doc/administration/geo/setup/external_database.md
(Link to current live version) -
doc/administration/geo/setup/index.md
(Link to current live version) -
doc/administration/geo/index.md
(Link to current live version) -
doc/administration/gitaly/index.md
(Link to current live version) -
doc/administration/gitaly/monitoring.md
(Link to current live version) -
doc/administration/gitaly/praefect.md
(Link to current live version) -
doc/administration/gitaly/reference.md
(Link to current live version) -
doc/administration/gitaly/troubleshooting.md
(Link to current live version) -
doc/administration/integration/plantuml.md
(Link to current live version) -
doc/administration/logs/index.md
(Link to current live version) -
doc/administration/logs/log_parsing.md
(Link to current live version) -
doc/administration/maintenance_mode/index.md
(Link to current live version) -
doc/administration/monitoring/gitlab_self_monitoring_project/index.md
(Link to current live version) -
doc/administration/monitoring/performance/grafana_configuration.md
(Link to current live version) -
doc/administration/monitoring/github_imports.md
(Link to current live version) -
doc/administration/monitoring/index.md
(Link to current live version) -
doc/administration/audit_events.md
(Link to current live version) -
doc/administration/docs_self_host.md
(Link to current live version) -
doc/administration/external_pipeline_validation.md
(Link to current live version) -
doc/administration/feature_flags.md
(Link to current live version) -
doc/administration/file_hooks.md
(Link to current live version) -
doc/administration/get_started.md
(Link to current live version) -
doc/administration/git_protocol.md
(Link to current live version) -
doc/administration/housekeeping.md
(Link to current live version) -
doc/administration/instance_limits.md
(Link to current live version) -
doc/administration/job_artifacts.md
(Link to current live version) -
doc/administration/load_balancer.md
(Link to current live version) -
doc/administration/merge_request_diffs.md
(Link to current live version) -
README.md
(Link to current live version) -
db/docs/deleted_tables/analytics_cycle_analytics_project_stages.yml
(Link to current live version) -
db/docs/deleted_tables/analytics_cycle_analytics_project_value_streams.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_cert_managers.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_cilium.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_crossplane.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_helm.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_ingress.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_jupyter.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_knative.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_prometheus.yml
(Link to current live version) -
db/docs/deleted_tables/clusters_applications_runners.yml
(Link to current live version) -
db/docs/deleted_tables/serverless_domain_cluster.yml
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Disabled eslint rules
The following files have disabled
eslint
rules. Please consider fixing them:app/assets/javascripts/achievements/constants.js
app/assets/javascripts/alerts_settings/constants.js
app/assets/javascripts/behaviors/preview_markdown.js
app/assets/javascripts/boards/components/board_settings_sidebar.vue
app/assets/javascripts/boards/constants.js
app/assets/javascripts/ci/pipeline_editor/components/editor/ci_config_merged_preview.vue
app/assets/javascripts/design_management/pages/design/index.vue
app/assets/javascripts/diffs/utils/merge_request.js
app/assets/javascripts/jobs/components/table/jobs_table_tabs.vue
app/assets/javascripts/labels/label_manager.js
app/assets/javascripts/lib/utils/url_utility.js
app/assets/javascripts/lib/graphql.js
app/assets/javascripts/monitoring/components/dashboard.vue
app/assets/javascripts/packages_and_registries/container_registry/explorer/components/details_page/tags_list.vue
app/assets/javascripts/packages_and_registries/container_registry/explorer/index.js
app/assets/javascripts/pages/projects/commit/show/index.js
app/assets/javascripts/pages/projects/project.js
app/assets/javascripts/projects/settings/access_dropdown.js
app/assets/javascripts/sidebar/components/labels/labels_select_vue/store/mutations.js
app/assets/javascripts/super_sidebar/components/user_bar.vue
app/assets/javascripts/vue_shared/components/markdown/header.vue
app/assets/javascripts/vue_shared/constants.js
app/assets/javascripts/deprecated_notes.js
app/assets/javascripts/merge_request_tabs.js
app/assets/javascripts/right_sidebar.js
Run the following command for more details
node_modules/.bin/eslint --report-unused-disable-directives --no-inline-config \ 'app/assets/javascripts/achievements/constants.js' \ 'app/assets/javascripts/alerts_settings/constants.js' \ 'app/assets/javascripts/behaviors/preview_markdown.js' \ 'app/assets/javascripts/boards/components/board_settings_sidebar.vue' \ 'app/assets/javascripts/boards/constants.js' \ 'app/assets/javascripts/ci/pipeline_editor/components/editor/ci_config_merged_preview.vue' \ 'app/assets/javascripts/design_management/pages/design/index.vue' \ 'app/assets/javascripts/diffs/utils/merge_request.js' \ 'app/assets/javascripts/jobs/components/table/jobs_table_tabs.vue' \ 'app/assets/javascripts/labels/label_manager.js' \ 'app/assets/javascripts/lib/utils/url_utility.js' \ 'app/assets/javascripts/lib/graphql.js' \ 'app/assets/javascripts/monitoring/components/dashboard.vue' \ 'app/assets/javascripts/packages_and_registries/container_registry/explorer/components/details_page/tags_list.vue' \ 'app/assets/javascripts/packages_and_registries/container_registry/explorer/index.js' \ 'app/assets/javascripts/pages/projects/commit/show/index.js' \ 'app/assets/javascripts/pages/projects/project.js' \ 'app/assets/javascripts/projects/settings/access_dropdown.js' \ 'app/assets/javascripts/sidebar/components/labels/labels_select_vue/store/mutations.js' \ 'app/assets/javascripts/super_sidebar/components/user_bar.vue' \ 'app/assets/javascripts/vue_shared/components/markdown/header.vue' \ 'app/assets/javascripts/vue_shared/constants.js' \ 'app/assets/javascripts/deprecated_notes.js' \ 'app/assets/javascripts/merge_request_tabs.js' \ 'app/assets/javascripts/right_sidebar.js'
Multiversion compatibility
This merge request updates GraphQL backend and frontend code.
To prevent an incident, ensure the updated frontend code is backwards compatible.
For more information, see the multiversion compatibility documentation.
Deprecated components
These deprecated components are in the process of being migrated. Please consider using Pajamas components instead.
- .alert
Pipeline Changes
This merge request contains changes to the pipeline configuration for the GitLab project.
Please consider the effect of the changes in this merge request on the following:
- Effects on different pipeline types
- Effects on non-canonical projects:
gitlab-foss
security
dev
- personal forks
- Effects on pipeline performance
Please consider communicating these changes to the broader team following the communication guideline for pipeline changes
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Aakriti Gupta (
@aakriti.gupta
) (UTC+2, 2 hours ahead of@joseph
)Etienne Baqué (
@ebaque
) (UTC-3, 3 hours behind@joseph
)frontend Minahil Nichols (
@minahilnichols
) (UTC-4, 4 hours behind@joseph
)Vitaly Slobodin (
@vitallium
) (UTC+2, 2 hours ahead of@joseph
)groupimport and integrate (backend) No engineer is available for automated assignment, please reach out to the #g_manage_import_and_integrate
Slack channel or mention@gitlab-org/manage/import-and-integrate
for assistance.Maintainer review is optional for groupimport and integrate (backend) groupimport and integrate (frontend) Justin Ho (
@justin_ho
) (UTC+7, 7 hours ahead of@joseph
)Maintainer review is optional for groupimport and integrate (frontend) ~"migration" No reviewer available No maintainer available maintenanceworkflow / maintenancepipelines for CI, Danger Madelein van Niekerk (
@maddievn
) (UTC+2, 2 hours ahead of@joseph
)David Dieulivol (
@ddieulivol
) (UTC+2, 2 hours ahead of@joseph
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
Rubygems
This merge request adds, or changes a Rubygems dependency. Please review the Gemfile guidelines.
Sidekiq queue changes
This merge request contains changes to Sidekiq queues. Please follow the documentation on changing a queue's urgency.
These queues were added:
cluster_agent:clusters_agents_notify_git_push
container_repository:container_registry_record_data_repair_detail
cronjob:packages_cleanup_delete_orphaned_dependencies
github_importer:github_import_pull_requests_import_merged_by
github_importer:github_import_pull_requests_import_review
bitbucket_server_import_advance_stage
bitbucket_server_import_import_lfs_object
bitbucket_server_import_import_pull_request
bitbucket_server_import_import_pull_request_notes
bitbucket_server_import_stage_finish_import
bitbucket_server_import_stage_import_lfs_objects
bitbucket_server_import_stage_import_notes
bitbucket_server_import_stage_import_pull_requests
bitbucket_server_import_stage_import_repository
bulk_imports_finish_batched_relation_export
bulk_imports_relation_batch_export
merge_requests_set_reviewer_reviewed
ssh_keys_update_last_used_at
cronjob:open_ai_clear_conversations
abuse_new_abuse_report
ci_llm_generate_config
compliance_management_framework_export_mailer
elastic_wiki_indexer
product_analytics_post_push
security_orchestration_configuration_create_bot
These queues had their attributes changed:
auto_merge:merge_trains_refresh
QA
e2e:package-and-test-ee
@joseph, the
package-and-test
job must complete before merging this merge request.*If there are failures on the
package-and-test
pipeline, ping your team's associated Software Engineer in Test (SET) to confirm the failures are unrelated to the merge request. If there's no SET assigned, ask for assistance on the#quality
Slack channel.Changes to utility SCSS files
Addition to
app/assets/stylesheets/framework/common.scss
You have added a new rule to
app/assets/stylesheets/framework/common.scss
. Are you sure you need this rule?If it is a component class shared across items, could it be added to the component as a utility class or to the component's stylesheet? If not, you can ignore this warning.
If it is a new utility class, is there another class that shares the same values in either this file or in
app/assets/stylesheets/utilities.scss
? If not, please add it toapp/assets/stylesheets/utilities.scss
, following the Gitlab UI naming style.Addition to
app/assets/stylesheets/utilities.scss
You have added a new rule to
app/assets/stylesheets/utilities.scss
. Are you sure you need this rule?If it is a component class shared across items, could it be added to the component as a utility class or to the component's stylesheet? If not, consider adding it to
app/assets/stylesheets/framework/common.scss
If it is a new utility class, is there another class that shares the same values in either this file or in
app/assets/stylesheets/utilities.scss
? If not, please be sure this addition follows the Gitlab UI naming style so it may be removed when these rules are included. See Include gitlab-ui utility-class library for more about this project.If needed, you can retry the
danger-review
job that generated this comment.You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
You're about to release the feature with the feature flag. This process can only be done after the global rollout on production. Please make sure in the rollout issue that the preliminary steps have already been done. Otherwise, changing the YAML definition might not have the desired effect.
When adding new CI tables, consider partitioning the table from the start if it references any of the larger CI tables:
ci_pipelines
,ci_stages
,ci_builds
,p_ci_builds_metadata
,ci_job_artifacts
,ci_pipeline_variables
.Generated by
DangerAllure report
allure-report-publisher
generated test report!e2e-review-qa:
test report for d55a30b6expand test summary
+-----------------------------------------------------------------------+ | suites summary | +------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------+--------+--------+---------+-------+-------+--------+ | Plan | 50 | 0 | 1 | 0 | 51 | ✅ | | Manage | 8 | 0 | 3 | 0 | 11 | ✅ | | Data Stores | 22 | 0 | 0 | 0 | 22 | ✅ | | Create | 27 | 0 | 1 | 0 | 28 | ✅ | | Verify | 10 | 0 | 0 | 0 | 10 | ✅ | | Govern | 24 | 0 | 0 | 3 | 24 | ❗ | | Monitor | 4 | 0 | 0 | 0 | 4 | ✅ | | Framework sanity | 9 | 0 | 1 | 0 | 10 | ✅ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | +------------------+--------+--------+---------+-------+-------+--------+ | Total | 154 | 0 | 7 | 3 | 161 | ❗ | +------------------+--------+--------+---------+-------+-------+--------+
unassigned @joseph