Diff error when adding repos to the otterdog config that already exist

[fredg02]

Opening an issue as @mbarbero suggested here https://github.com/eclipse-arrowhead/.eclipsefdn/pull/2#issuecomment-3225822445.

I assume the bug is supposed to be opened for the errors shown here: https://github.com/eclipse-arrowhead/.eclipsefdn/pull/2#issuecomment-3225819333

@mbarbero please add more details if required.

[netomi]

so that looks like the repo was created manually and then a PR was created to adapt the configuration.

The way the system has been setup for now is that PRs are there for project members to alter the configuration. If you as admin make changes, opening a PRs for that change does not make sense. You should do the changes locally and apply them, and afterwards push the configuration. You can add a commit message for traceability.

When opening a PRs also the changes are not applied by comparing to the live configuration, but to the currently checked in configuration, as it is supposed to handle only changes. Thats why you get an error when the repo already exists on GitHub: otterdog does not know in a PR, as it will create a diff to the last checked in configuration and apply the changes.

This can be changed ofc (we always compared to the live settings before), but that has other implications, as for large orgs with lots of repos, this could lead to rate limit issues.