Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update config_norm_rules.json #3780

Merged
merged 1 commit into from
Jan 8, 2025
Merged

Update config_norm_rules.json #3780

merged 1 commit into from
Jan 8, 2025

Conversation

watson
Copy link
Contributor

@watson watson commented Jan 8, 2025

Motivation

This needs to be in sync with the dd-go repo, otherwise tests might
fail.

Changes

Copied over the newest file.

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • If PR title starts with [<language>], double-check that only <language> is impacted by the change
  • No system-tests internal is modified. Otherwise, I have the approval from R&P team
  • CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
  • A scenario is added (or removed)?

This file is copied from the dd-go repo
@watson watson requested a review from a team as a code owner January 8, 2025 06:49
Copy link
Contributor Author

watson commented Jan 8, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@watson watson merged commit 015482e into main Jan 8, 2025
280 of 281 checks passed
@watson watson deleted the watson/update-norm-rules branch January 8, 2025 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants