Move deploy history report to standalone page #28202
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
…ions, use f-strings
stickler-ci
reviewed
Jul 24, 2020
corehq/apps/hqadmin/reports.py
Outdated
|
|
||
| from datetime import datetime as dt |
There was a problem hiding this comment.
F401 'datetime.datetime as dt' imported but unused
esoergel
approved these changes
Jul 24, 2020
esoergel
added
the
product/admin
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.
#27839
One feature of the above CEP.
Please note this is re-upload of another PR (#28133), in which I messed up a rebase. Please look there for the original comments on my PR.
SUMMARY
Moved the Deploy History Report previously found on the 'System Info' admin page to its own standalone page. Part of a larger process of adding a commit field to the deploy history as explained in the above issue.
PRODUCT DESCRIPTION
Users will now be able to access the 'deploy history report' on its own standalone page.