Nicholas

@MoritzWeber0, few questions--right now the git_instances table has types for GITHUB, GITLAB, AZUREDEVOPS, and GENERAL. 1. Do we need to worry about GENERAL? I'd probably just show a message saying...

@MoritzWeber0 -- questions! Linking to author profile: I should be able to link to a commit author's Collab profile if they used the same email for both the Collab Manager...

Note to future self: be more careful not to ignore default assignments and break the tests 😆 Assigning fields to something like `name: str | None = None` requires shifting...

codecov/patch is failing, but the new code doesn't add or meaningfully change the existing functions, it looks like [backend/capellacollab/settings/modelsources/t4c/repositories/routes.py](https://app.codecov.io/gh/DSD-DBS/capella-collab-manager/commit/6f53fcece46d7cc5400f6fb947d8accf3bf9b677/blob/backend/capellacollab/settings/modelsources/t4c/repositories/routes.py) is just already missing some coverage.

@dominik003 made a nice dent in this with #1465, but it begged the question of exactly what, how, and where to update. For general testability and reviewer sanity I'd probably...

Rough idea, but what do you think of this @MoritzWeber0? - basic error pydantic models - a function to create error responses - generating responses just above each route so...

Ugh, just realized raising the exception that way would break the existing error interceptor. So it seems like it would require even more duplication, because you'd need to repeat everything...

UI thoughts: I'd prioritize having an explicit section at the top for elements that would be at risk of merge errors--this would ideally appear for everyone who either opens an...

Discussed with Moritz: - At risk open elements should be at risk open models and display _all_ open elements in that model (because changes in one element can actually impact...