Update fetchCommitPage to not specify Since #53
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
In its previous state, fetchCommitPage checked for commits solely from the point at which the user joined a specific GitLab instance during the initial load. This amendment uses check of the entire commit history.
|
Thanks for the PR. I'll review and merge it later today or tomorrow. |
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.
In its previous state, fetchCommitPage checked for commits solely from the point at which the user joined a specific GitLab instance during the initial load. This amendment uses a check of the entire commit history.
Use case:
We have migrated from a public GitLab.com to a privately hosted Gitlab instance. Therefore, the users are newer than most of their commit history.
This does change the behavior of the importer, so not sure if it should be accepted.