GDCD and DODEC fixups: date handling #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cbullinger
approved these changes
Jan 8, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
findOldestBackupfunc to correctly identify December as older than Jan across year boundaries (and therefore drop the correct "oldest" backup)parse-logs.goscript that more accurately identifies moved vs. new content to also output the total count that GDCD reports, so we can manually adjust monthly counts as needed (i.e. total count minus actual count after calculating moved tells us how much to remove from the monthly numbers when we run them). This is mainly to adjust for the comprehensive coverage projects that show a lot of content as "net new" in GDCD when it's actually just moved.