check_for_modifications should not be required - #53
Merged
Conversation
…ough logic to handle if check_for_modifications is not specified
Collaborator
|
Re-established the existing parser behavior and verified there's enough logic to handle if check_for_modification is not specified in config. You can close this request. Note: If check_for_modifications is not specified in the config then the parser would look only for new files and will miss if any modifications done to the existing files. |
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
2 participants
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.
One of the recent PRs added functionality to check for modification based on the the last_modified time of files, but this required a value in the source config that broke existing parsers