fix: use timestamp of commit instead of updatestamp in get_or_update_branch_head #356
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose/Motivation
timestamp
is the field which we were using before to decide if a commit was to be branch's head or not. The issue with ordering byupdatestamp
is thatupdatestamp
is nullable which leads to incorrect behaviour where we may pick a commit from very long ago to be the branch head.What does this PR do?