You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current version, the configuration server will fail in certain scenarios when calculating the common ancestor of certain commits. This is required e,g. for getting the users which modified a file.
In the current logic, it is not handled if a commit is reachable from multiple child commits. Another problem is if no common ancestor exists which can happen (in version 1.12.1) due to an initial configuration sync using remote repositories.
The text was updated successfully, but these errors were encountered:
In the current version, the configuration server will fail in certain scenarios when calculating the common ancestor of certain commits. This is required e,g. for getting the users which modified a file.
In the current logic, it is not handled if a commit is reachable from multiple child commits. Another problem is if no common ancestor exists which can happen (in version 1.12.1) due to an initial configuration sync using remote repositories.
The text was updated successfully, but these errors were encountered: