Repository navigation
Compare pullr with gita, gitup, myrepos and mani - #7
Merged
Merged
Conversation
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
1 participant
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.
Adds a "How it compares" section to the README: runtime, how repos are found, parallelism, update command, merge commits, local changes and dry run for pullr, gita, gitup, myrepos and mani. Each cell comes from the tool's own source at its current HEAD.
The note under the table explains the bounded default parallelism with measurements: a self-hosted GitLab over SSH dropped connections from 16 parallel fetches up (6-14 spurious failures), consistent with OpenSSH's default
MaxStartups 10:30:100, while 8 produced none. GitHub handled all 64 repositories at once over SSH and HTTPS without errors.