Currently, stored commit data doesn't quite give me the information I'm needing...
Committer date and author date are not 100% reliable for dividing a commit history up by release or branch.
A PR created before a release but merged after can have earlier dates… — this can be quite frustrating if you're trying to pin down commits for a release: It should be there!, but then isn't. (This gets worse using release branches.)
Would you be open to adding the sha of a parent of a commit to the commit table? (As an FK? 🤔 — likely not feasible.)
I think this list should only have a single entry. (🤔 — not sure why it's a list then...)
With this it would be possible to build/reconstruct a chain of commits from the history, that I don't think is available as yet (unless you know a better way).
It is certainly possible to get sequential lists of commits out of git directly, so the same would be possible combining tools, but wondering if a single tool could do it.
Hi @simonw đź‘‹
Currently, stored commit data doesn't quite give me the information I'm needing...
Committer date and author date are not 100% reliable for dividing a commit history up by release or branch. A PR created before a release but merged after can have earlier dates… — this can be quite frustrating if you're trying to pin down commits for a release: It should be there!, but then isn't. (This gets worse using release branches.)
Would you be open to adding the
sha
of aparent
of a commit to the commit table? (As an FK? 🤔 — likely not feasible.)It's part of the response body:
I think this list should only have a single entry. (🤔 — not sure why it's a list then...)
With this it would be possible to build/reconstruct a chain of commits from the history, that I don't think is available as yet (unless you know a better way).
It is certainly possible to get sequential lists of commits out of git directly, so the same would be possible combining tools, but wondering if a single tool could do it.
What do you think? Thanks! 🏅