#477 and #178 Misc bugfixes and small edits to the initial Version/Library import and the monthly refresh #481
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.
Closes #477. Part of #178.
.gitmodules
and there is not currently another way to get that dataLibraryVersion
requiredupdate_library()
more generic and only updating the db, and moving the other update methods to within the loop inupdate_libraries()
. Also added calls to get PR and issue data that were missing before (methods were there, just not called), but commented it out. It's data that takes a long time to pull, so we may want to either break up the process into celery tasks, or add logic to handle rate limiting, or both. CC @4down @frankwiles since this PR/commit data appears on the new homepage I think?./manage.py update_libraries
), but only the most recent month in the monthly refresh task