Uh oh!
There was an error while loading. Please reload this page.
Update CODEOWNERS to new team members - #16
Merged
Merged
Conversation
Signed-off-by: Christian Leucht <c.leucht@syde.com>
tfrommen
approved these changes
Aug 12, 2026
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
updates codeowners to
* @inpsyde/platform-engineering.What is the current behavior? (You can also link to an open issue here)
Accounts are mentioned directly. This puts the responsibility on 2 persons instead of a team which should take care of that repository.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
yes
Security impact
none.