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
The data we're sorting has clusters of duplicates in the input, because
`dirname` reduces all repos in the same network (i.e., forks) to the same
network path. Running `uniq` before `sort` eliminates those duplicates,
which means `sort` requires less CPU and RAM to do its thing.
We still need `uniq` on the output end, because there's no guarantee that
all duplicates in the input are clustered.
I've run tests, and the cost of `uniq` is small enough that it does no
harm if the input has no duplicates at all.
git --no-pager diff --unified=0 --no-prefix -- $tempdir/source_routes $tempdir/destination_routes ||echo"Warning: One or more repository networks and/or gists were not found on the source appliance. Please contact GitHub Enterprise Support for assistance."
git --no-pager diff --unified=0 --no-prefix -- $tempdir/source_routes $tempdir/destination_routes ||echo"Warning: One or more storage objects were not found on the source appliance. Please contact GitHub Enterprise Support for assistance."
0 commit comments