Move common-util into reporting-pipeline-service#795
Merged
Conversation
ericbuckley
reviewed
May 5, 2026
ericbuckley
approved these changes
May 6, 2026
Contributor
ericbuckley
left a comment
ericbuckley
left a comment
There was a problem hiding this comment.
Looks good, just some questions on whether we need to merge plugins/deps specified in the common-util subproject into the reporting-pipeline-service subproject
eliSkylight
approved these changes
May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Moves the
common-utilcode into the reporting-pipeline-service. Theres no need to have a shared library when its a single service...Related Issue
🤠
Checklist