when determining archive age, fall-back to updated time #977
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
The created field in a request can potentially be None. If so, fall back to using the updated field in order to determine the age of a request. Signed-off-by: Taylor Madore <tmadore@redhat.com>
ben-alkov
approved these changes
Feb 6, 2024
eskultety
approved these changes
Feb 7, 2024
Merged
via the queue into
containerbuildsystem:master
with commit Feb 7, 2024
0f73ead
14 checks passed
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.
The created field in a request can potentially be None. If so, fall back to using the updated field in order to determine the age of a request.
Something I knew about and missed 😓. The created field was added later, but the updated field has been there since the beginning and should be approximately the same.
Maintainers will complete the following section