Syncs YouTube channels and playlists to a locally hosted media server
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 91%
Response Time: 7d
First Timer Success: 100%
meeb/tubesync has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in meeb/tubesync respond to incoming external pull requests in approximately 164.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 65.4 places meeb/tubesync in the A tier.
The external contributor pull request merge rate for meeb/tubesync is 90.7%, based on public PR activity from non-core contributors.
meeb/tubesync currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in meeb/tubesync. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/meeb/tubesync?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~107 hours (96% approval). Large PRs (>500 lines) take ~791 hours (41% approval). Keep your diff compact for rapid review.
Somewhat related: https://github.com/masterdot/tubesync/blob/docs/ruff-concept/docs/ruff-concept-2026-09-08.md tubesync/common/errors.py tubesync/common/hat_busybox.py tubesync/common/logger.py tubesync/common/logs/__init__.py tubesync/common/logs/_filters.py tubesync/common/logs/syslog/hat/__main__.py tubesync/common/logs/syslog/hat/_default.py tubesync/common/middleware.py tubesync/common/queue_with_peek.py tubesync/common/tests.py tubesync/common/timestamp.py tubesync/common/views.py tubesync/hat-syslog_tool.py tubesync/healthcheck.py tubesync/sync/fields.py tubesync/sync/forms.py tubesync/sync/hooks.py tubesync/sync/management/commands/create-tvshow-nfo.py tubesync/sync/management/commands/delete-source.py tubesync/sync/management/commands/fix-mariadb.py tubesync/sync/management/commands/import-existing-media.py tubesync/sync/matching.py tubesync/sync/mediaservers.py tubesync/sync/models/__init__.py tubesync/sync/models/_private.py tubesync/sync/models/me
Currently there is duplication. For new sources we are essentially running two indexing tasks. After #1561 was merged, we are downloading far less than the normal indexing task. tubesync/tubesync/sync/models/source.py Lines 484 to 488 in 7ee8c96 @property def get_image_url(self): return get_youtube_image_info(self.url) tubesync/tubesync/sync/youtube.py Lines 83 to 148 in 7ee8c96 def get_image_info(url): avatar_url = None banner_url = None
Do you think it is worth adding a setting to consistently choose either original or default formats? Yes that sounds like a nice per-source toggle to have available. It's probably more of a documentation challenge rather than the feature itself to accurately communicate what it does to people. Originally posted by @meeb in #1452 (comment) My first idea was to just use a setting that would apply to all sources.
This requires the Codec data to be populated: #1458 Orientation is one of: landscape portrait Thumbnail table partial example: extension Codec min_height max_height resized_height min_width max_width resized_width orientation resized jpg [Codec.pk of <thumbnail,jpg>] 360 1080 NULL 480 1920 NULL landscape False webp [Codec.pk of <thumbnail,webp>] 360 1080 720 480 1920 1280 landscape False
The common codecs used by video formats should be added to the data migration for our new Codec model / table. We need at least these entries: av1 avc1 hev1 hvc1 vp9 You are welcome to expand the migration that I already made for subtitle codecs. https://github.com/meeb/tubesync/blob/issue/1419/design-generic-models/tubesync/sync/migrations/0039_codec_data.py
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to meeb/tubesync, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of meeb/tubesync acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.7% were successfully merged into the primary branch.
meeb/tubesync has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 65.4 places meeb/tubesync in the Welcoming tier.
The external pull request merge rate is 90.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, meeb/tubesync currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for meeb/tubesync are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.