Closed
Conversation
1fe718d to
4f10c76
Compare
dcd761a to
a977c46
Compare
Contributor
Author
|
As new logic still will miss data, will tackle this later |
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
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.
Summary
As tapd hasn't been used very frequently, so there are some issues when collecting by incremental
modifiedwhich is used in url, as tapd time are all in China, but we store all data as UTC time in db, so we need to transform time to CstZonesince.In(CstZone).Format("2006-01-02")modifiedwill not be changed.taskused a wrong tagnamefor the fieldtitleDoes this close any open issues?
Relate to #3632
Screenshots
Include any relevant screenshots here.
Other Information
this new way still has side effect, we cannot collect story commits for the story which already collected commits and never got modified after last collection