[go: up one dir, main page]

Assign target_type to new push events

What does this MR do and why?

Assign target_type=project to new push events

Query Plans

Before After
Contribution analytics aggregator https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43245/commands/132152 https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43245/commands/132160
Code suggestion events finder https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43245/commands/132166 https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43245/commands/132170
Manage > Activity > Push Events https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43245/commands/132173 https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43245/commands/132171

References

Related to #568267 (closed)

Screenshots or screen recordings

Before After
Screen_Recording_2025-09-05_at_3.49.57_PM Screen_Recording_2025-09-05_at_3.52.44_PM

How to set up and validate locally

  1. Generate a new push event by pushing changes to a branch.
    • Tip: You may also simply create a project which generates a created and pushed event.
  2. Go to /api/v4/events?sort=desc&target_type=project and verify the a push event is logged.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Shane Maglangit

Merge request reports

Loading