commit-report-sync

scubbo/commit-report-sync

Fork 0

Commit Graph

Author	SHA1	Message	Date
Commit Report Sync Bot	5f6018c6cd	Remove reference to parentHashes Turns out they're not actually needed, because the implementation of "finding all commits" just iterates over the lines of the `git log` output, anyway - no need to actually traverse the tree. I am _reasonably_ sure this means that it's no longer a pre-requisite that the source repo has linear history, either. If I discover during adding tests that that actually is the case, I'll re-add that note.	2025-03-02 21:49:11 -08:00
Commit Report Sync Bot	4b691bbe6c	Add TODO.txt	2025-03-01 23:56:53 -08:00
Jack Jackson	948a615fcc	First working commit (though running in Actions might require some authentication tweaks)	2025-03-01 22:34:06 -08:00

Author

SHA1

Message

Date

Commit Report Sync Bot

5f6018c6cd

Remove reference to parentHashes

Turns out they're not actually needed, because the implementation of
"finding all commits" just iterates over the lines of the `git log`
output, anyway - no need to actually traverse the tree.

I am _reasonably_ sure this means that it's no longer a pre-requisite
that the source repo has linear history, either. If I discover during
adding tests that that actually is the case, I'll re-add that note.

2025-03-02 21:49:11 -08:00

Commit Report Sync Bot

4b691bbe6c

Add TODO.txt

2025-03-01 23:56:53 -08:00

Jack Jackson

948a615fcc

First working commit (though running in Actions might require some authentication tweaks)

2025-03-01 22:34:06 -08:00

3 Commits