[v4.4] Optimize copybara sync behavior for specific no-change scenarios

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • 35
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There are two cases we need to capture if there are two syncs from 10gen/mongo to mongodb/mongo, we already handled the first one. but after we start to combine enterprise repo we will need to address the second case as well. 

      1: Repositories are identical (“No new changes to import…”) 

      2: Differences exist but do not affect the destination due to exclusion rules or specific configurations (“Iterative workflow produced no changes…”)

              Assignee:
              Juan Gu (Inactive)
              Reporter:
              Juan Gu (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: