phil - jankaritech

phil commented on pull request JankariTechUG/GitTrustedTimestamps#12

2025-06-03 11:44:03 +00:00

feature: validate commits in reverse date-time order when MAX_COMMITS_TO_CHECK is used

Sample output from running on the JankariTechUG/accounting repo:

phil@phil-Inspiron-5468:~/git/JankariTechUG/accounting$ ~/git/JankariTechUG/GitTrustedTimestamps/hooks/validate.sh --maxcommit…

phil created pull request JankariTechUG/GitTrustedTimestamps#12

2025-06-03 11:40:14 +00:00

feature: validate commits in reverse date-time order when MAX_COMMITS_TO_CHECK is used

phil created branch date-order in JankariTechUG/GitTrustedTimestamps

2025-06-03 11:39:41 +00:00

phil pushed to date-order at JankariTechUG/GitTrustedTimestamps

2025-06-03 11:39:41 +00:00

d48097695b feature: validate commits in reverse date-time order when MAX_COMMITS_TO_CHECK is used

phil opened issue JankariTechUG/GitTrustedTimestamps#11

2025-06-03 04:15:20 +00:00

Validate latest timestamp commits first

phil pushed to main at JankariTechUG/GitTrustedTimestamps

2025-06-02 11:40:12 +00:00

1622c1244f Merge pull request 'fix: stop correctly when MAX_COMMITS_TO_CHECK is reached' (#10) from respect-MAX_COMMITS_TO_CHECK into main

f712aa0822 chore: adjust comment about MAX_COMMITS_TO_CHECK

8aba6e98d1 fix: stop correctly when MAX_COMMITS_TO_CHECK is reached

Compare 3 commits »

phil merged pull request JankariTechUG/GitTrustedTimestamps#10

2025-06-02 11:40:10 +00:00

fix: stop correctly when MAX_COMMITS_TO_CHECK is reached

phil pushed to respect-MAX_COMMITS_TO_CHECK at JankariTechUG/GitTrustedTimestamps

2025-06-02 09:48:00 +00:00

f712aa0822 chore: adjust comment about MAX_COMMITS_TO_CHECK

phil commented on pull request JankariTechUG/GitTrustedTimestamps#10

2025-06-02 08:55:39 +00:00

fix: stop correctly when MAX_COMMITS_TO_CHECK is reached

Note: there is also an issue with the way that the tree of parent commits typically end up being traversed. That is a separate issue, and I will think about how to improve that.

phil created pull request JankariTechUG/GitTrustedTimestamps#10

2025-06-02 08:48:52 +00:00

fix: stop correctly when MAX_COMMITS_TO_CHECK is reached

phil pushed to respect-MAX_COMMITS_TO_CHECK at JankariTechUG/GitTrustedTimestamps

2025-06-02 08:48:02 +00:00

8aba6e98d1 fix: stop correctly when MAX_COMMITS_TO_CHECK is reached

phil created branch respect-MAX_COMMITS_TO_CHECK in JankariTechUG/GitTrustedTimestamps

2025-06-02 08:48:02 +00:00

phil commented on issue JankariTechUG/GitTrustedTimestamps#8

2025-06-02 04:14:51 +00:00

Reduce the time taken to validate the commit chain

merge commits don't have a timestamp in our case, but in theory could. Do commits without any stamp also take so much time to be validated?

The validation code "skips" quickly through…

phil merged pull request JankariTechUG/GitTrustedTimestamps#9

2025-06-02 04:10:48 +00:00

feature: limit the number of commits to be validated

phil pushed to main at JankariTechUG/GitTrustedTimestamps

2025-06-02 04:10:48 +00:00

31e44f9b70 Merge pull request 'feature: limit the number of commits to be validated' (#9) from limit-num-commits-validated into main

4437b66f67 feature: default to checking all commits

aabd314dde feature: limit the number of commits to be validated

Compare 3 commits »

phil closed issue JankariTechUG/GitTrustedTimestamps#8

2025-06-02 04:10:48 +00:00

Reduce the time taken to validate the commit chain

phil commented on pull request JankariTechUG/GitTrustedTimestamps#9

2025-05-29 04:21:37 +00:00

feature: limit the number of commits to be validated

Done 0 means "infinity" and is now the default.

phil pushed to limit-num-commits-validated at JankariTechUG/GitTrustedTimestamps

2025-05-29 04:11:27 +00:00

4437b66f67 feature: default to checking all commits

phil created pull request JankariTechUG/GitTrustedTimestamps#9

2025-05-28 05:12:37 +00:00

feature: limit the number of commits to be validated

phil created branch limit-num-commits-validated in JankariTechUG/GitTrustedTimestamps

2025-05-28 05:11:34 +00:00