phil
0 Followers · 0 Following
Joined on 2025-01-10
Repositories Projects Packages Code Public Activity Starred Repositories
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 created branch respect-MAX_COMMITS_TO_CHECK in JankariTechUG/GitTrustedTimestamps 2025-06-02 08:48:02 +00:00
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 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 closed issue JankariTechUG/GitTrustedTimestamps#8 2025-06-02 04:10:48 +00:00
Reduce the time taken to validate the commit chain
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 merged pull request JankariTechUG/GitTrustedTimestamps#9 2025-06-02 04:10:48 +00:00
feature: limit the number of commits to be validated
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 pushed to limit-num-commits-validated at JankariTechUG/GitTrustedTimestamps 2025-05-28 05:11:34 +00:00
aabd314dde 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
phil opened issue JankariTechUG/GitTrustedTimestamps#8 2025-05-28 05:08:29 +00:00
Reduce the time taken to validate the commit chain
phil commented on pull request JankariTechUG/GitTrustedTimestamps#7 2025-03-18 08:27:27 +00:00
only validate each commit once

I need to do the timestamp validation thing for PRs in this repo - I will sort that out in a while.

phil commented on pull request JankariTechUG/GitTrustedTimestamps#7 2025-03-18 08:25:48 +00:00
only validate each commit once

Without this change, the local run time for me is "long" (probably a few hours, I will leave it running and report later)

phil commented on pull request JankariTechUG/GitTrustedTimestamps#7 2025-03-18 08:14:23 +00:00
only validate each commit once

A run of this locally:

phil created pull request JankariTechUG/GitTrustedTimestamps#7 2025-03-18 08:13:40 +00:00
only validate each commit once
phil created branch validate-each-commit-once-only in JankariTechUG/GitTrustedTimestamps 2025-03-18 08:03:10 +00:00