Skip to content

Conversation

nbbeeken
Copy link
Contributor

@nbbeeken nbbeeken commented Mar 21, 2025

Description

What is changing?

NODE-6871

Is there new documentation needed for these changes?

What is the motivation for this change?

Tagging the composite scores accurately and making sure we don't miss tags in the future.

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@nbbeeken nbbeeken requested a review from a team as a code owner March 21, 2025 15:18
@nbbeeken nbbeeken force-pushed the NODE-6871-fix-perf-tags-2 branch from 9b2185c to 8600608 Compare March 21, 2025 15:21
@dariakp dariakp self-assigned this Mar 21, 2025
@dariakp dariakp added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Mar 21, 2025
@dariakp dariakp merged commit 892c14d into main Mar 21, 2025
25 of 29 checks passed
@dariakp dariakp deleted the NODE-6871-fix-perf-tags-2 branch March 21, 2025 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Primary Review In Review with primary reviewer, not yet ready for team's eyes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants