Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
1. stuff gets merged into the git main branch 2. git records two parents to each merge, the main branch (first), and the branch it's coming fro (second) 3. and if you do git log by default you'll get... a mishmash of everything? And our since 24 hours ago seems to find commits on this branch that's getting merged in 4. we took the before-oldest 24h old commit for that, which happened to be ancient, I think 5. and then when we did git diff of course it picked up commits from the most recently merged branch which had been branched loooong ago, before all of those tutorials were added 6. so we did git diff that to main and got a long list of changed files that weren't 'true' 7. I think adding --first-parent will ensure that it'll pick the right commit on the right branch to compare to
- Loading branch information