Workflow often just reorder resolvers.txt rather than making real changes

[berney]

The workflow runs off the existing resolvers.txt and commits the results back. But the order is nondeterministic, so it often just changing the ordering in the file.

Looking at the last 683 commits (1y2m), there's been no real changes, if we sort the file:

for c in $(git log --format="%h" -n 683); do git show "$c":resolvers.txt | sort | md5sum; done | sort | uniq -c
    683 88ed3d61baa70f89764f6477540ccc5c  -

The last real change was 59b240f:

diff <(git show 59b240f:resolvers.txt | sort ) <(cat resolvers.txt | sort)

9d8
< 80.67.169.12

IIUC slowly overtime resolvers are being removed, but I don't think new ones can be added.

IMO it would be better to sort the file in the workflow and then only commit if there is a change.