Always backfill all GitHub data on every run #51
Merged
Conversation
This file contains 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
ghickman
force-pushed
the
always-be-backfillin
branch
3 times, most recently
from
9e3c6dd to
620667c
Compare
We're moving to replacing all the data every day, since that's what we've ended up doing more often than not and it's already quite fast!
ghickman
force-pushed
the
always-be-backfillin
branch
from
620667c to
91c6289
Compare
benbc
approved these changes
Nov 28, 2023
This was referenced Nov 28, 2023
Merged
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.
While working on the GitHub data we realised that I had been backfilling after every major change to the code, and that the frequency at which we wrote the data was more than fast enough to do this in production too.