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
When a commit is pushed to a mirrored repository, the expectation is that any changes made by users are overwritten during the next mirroring process. However, this is not happening as expected.
The root cause lies in Central Dogma's limited check, which solely examines the stored local revision—unchanged by the user's commit—against the remote head.
Hello @minwoox, I would like to take this issue, but still confused. Could you give me an example of what is expected and the current status, so I can try to reproduce it?
Say, there is Git repository A mirrored to Central Dogma repository B.
The content of A and B should be the same except for mirror_state.json. If some content is pushed to B repository, it should be overwritten by the content of A.
Currently, the changes pushed to B do not update mirror_state.json so the head revision comparison can't detect new commits in B.
We may solve the problem by storing the latest revision of B mirrored to mirror_state.json.
When a commit is pushed to a mirrored repository, the expectation is that any changes made by users are overwritten during the next mirroring process. However, this is not happening as expected.
The root cause lies in Central Dogma's limited check, which solely examines the stored local revision—unchanged by the user's commit—against the remote head.
centraldogma/server-mirror-git/src/main/java/com/linecorp/centraldogma/server/internal/mirror/AbstractGitMirror.java
Line 356 in 03540a1
The text was updated successfully, but these errors were encountered: