populate_history command: support for --default-date #1494
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
The-Alchemist
force-pushed
the
feature/populate_history-with-custom-date
branch
from
7cd19f0 to
b07b29a
Compare
|
@treyhunner, @ddabble : Any feedback? 🙏 |
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.
Description
manager.py populate_history --default-date=1970-01-01Motivation and Context
It's very handy to specify a
default-datefor thepopulate_historycommand.For our use case, we want to set the date to
1970-01-01to make sure all the historical entries are older than everything else in the system.How Has This Been Tested?
See unit tests. Feedback welcome!
Types of changes
Checklist:
pre-commit runcommand to format and lint.AUTHORS.rstCHANGES.rst