sometimes, the activities get returned in the same order as before, and sometimes the order is completely different. that leads to misleading git diff views in merge requests / pull requests.
the order seems to be randomized when changes are made and even the activity ids get renewed.
what stays the same is the activity key -- so lets sort by that when saving the json?
github-actions[bot]
commented
1 month ago
sometimes, the activities get returned in the same order as before, and sometimes the order is completely different. that leads to misleading git diff views in merge requests / pull requests.
the order seems to be randomized when changes are made and even the activity ids get renewed. what stays the same is the activity key -- so lets sort by that when saving the json?
needs to be tested if it messes things up :D