The current algorithm of validate.sh traverses the tree of parent commits recursively by following one side to its end, then backing up to the previous commit that had multiple parents and going down that side... The result is that very often the oldest timestamp commits are found first in the traversal and checked. When there is a limit on the number of commits to be checked, this means that some of the most recent timestamp commits do not get checked.
Provide a different algorithm that processes the commits in reverse date order.
The current algorithm of `validate.sh` traverses the tree of parent commits recursively by following one side to its end, then backing up to the previous commit that had multiple parents and going down that side... The result is that very often the oldest timestamp commits are found first in the traversal and checked. When there is a limit on the number of commits to be checked, this means that some of the most recent timestamp commits do not get checked.
Provide a different algorithm that processes the commits in reverse date order.
phil
self-assigned this 2025-06-03 04:15:20 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The current algorithm of
validate.shtraverses the tree of parent commits recursively by following one side to its end, then backing up to the previous commit that had multiple parents and going down that side... The result is that very often the oldest timestamp commits are found first in the traversal and checked. When there is a limit on the number of commits to be checked, this means that some of the most recent timestamp commits do not get checked.Provide a different algorithm that processes the commits in reverse date order.