Fix inconsistent commit ordering for git log

[jovnc]

Exercise Review

Exercise Discussion

Fix #212

Checklist

• If you require a new remote repository on the Git-Mastery organization, have you created a request for it?
• Have you written unit tests using repo-smith to validate the exercise grading scheme?
• Have you tested your changes using the instructions posted?
• Have you verified that this exercise does not already exist or is not currently in review?
• Did you introduce a new grading mechanism that should belong to git-autograder?
• Did you introduce a new dependency that should belong to app?

[damithc]

Thanks for the quick fix, @jovnc
We probably want to document the rationale for this 'odd' behaviour somewhere (as a comment?)

[jovnc]

@woojiahao I'll rebase against the main branch and test the bot again later

[VikramGoyal23]

LGTM!

[jovnc]

@VikramGoyal23 Can you review the added comments?

[jovnc]

@woojiahao The comment action only runs on newly created PR, maybe we can test it out in a new PR

[woojiahao]

It failed again: https://github.com/git-mastery/exercises/actions/runs/20695329443/job/59458055297

I'm starting to suspect it has something to do with the GITHUB_TOKEN because it works when I create the PR

[VikramGoyal23]

LGTM, the comments are sufficient to document the reasoning. Should we make a separate note somewhere else noting that the revision graph is jumbled up without the sleep statement? Or is that intuitive enough for a newcomer?

[jovnc]

@VikramGoyal23 I'll merge this in first, this is good enough for now, I believe this is good enough for now and can serve as an example to future contributors of such an issue. If we encounter this again in the future, we will be aware of it.