Theme Boost Union is an enhanced child theme of Boost which is intended, on the one hand, to make Boost simply more configurable and, on the other hand, to provide helpful additional features for the daily Moodle operation of admins, teachers and students.
C-Rank Grade: D (Risky) - 21/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
moodle-an-hochschulen/moodle-theme_boost_union has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in moodle-an-hochschulen/moodle-theme_boost_union respond to incoming external pull requests in approximately 0.0 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 20.8 places moodle-an-hochschulen/moodle-theme_boost_union in the D tier.
The external contributor pull request merge rate for moodle-an-hochschulen/moodle-theme_boost_union is 0.0%, based on public PR activity from non-core contributors.
moodle-an-hochschulen/moodle-theme_boost_union currently has 15 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Theme Boost Union is an enhanced child theme of Boost which is intended, on the one hand, to make Boost simply more configurable and, on the other hand, to provide helpful additional features for the daily Moodle operation of admins, teachers and students.
Collaborative maintainer environment in moodle-an-hochschulen/moodle-theme_boost_union. Reviews community pull requests with focus on project quality.
Discussions in moodle-an-hochschulen/moodle-theme_boost_union focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/moodle-an-hochschulen/moodle-theme_boost_union?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Up to now, the Course related hints for teachers which are configured in Boost Union are, up to now, not shown if the course is using the single activity format. This is because the hints check if the user is on /course/view.php before showing the notification. And there is no /course/view.php in the single activity format. The only exception is the showswitchedroleincourse hint which is shown on all course and activity pages and does not have such a URL check. The improvement proposal would be to check first if the course is in the single activity format and, if yes, to skip the URL check and to show the hint on all course (and activity) pages. Alternatively, BU could identify the "main" page of the configured particular activity (e.g. /mod/forum/view.php for mod_forum) and to change the URL check to that URL.
This is a follow-up of #1130 / #1206: Currently, if theme_boost_union | loginshibbolethinternalwayf is enabled, the internal WAYF is composed with the default strings from auth_shibboleth: These are the string sources: auth_shibboleth_select_organization, auth_shibboleth auth_shibboleth_select_member, auth_shibboleth auth_shib_contact_administrator, auth_shibboleth It would be worthwhile to have Boost Union settings to customize these strings which are unhidden in the settings as soon as theme_boost_union | loginshibbolethinternalwayf is enabled
This is a follow-up of #1130 / #1206: Currently, if theme_boost_union | loginshibbolethinternalwayf is enabled, the internal WAYF shows an organization selector form: This form can already be submitted if no organization is selected yet and ends up on an ugly Moodle page in this case: It would be worthwhile to prevent that the form is submitted until an organization is selected
This is a follow-up of #1130 / #1206: Currently, if theme_boost_union | loginidpsplit is enabled, multiple IdP buttons are split into multiple tabs / accordeon elements: However, as described in the setting's description, the labels of the tabs / accordeon elements are currently taken from the auth method settings. There isn't a possibility to configure the labels directly in Boost Union. It would be worthwhile to add settings to Boost Union which allow the admin to set these labels in this special case as well directly in Boost Union.
This is a follow-up to #709 It would be worthwhile to add a setting to Feel -> Links -> Special links markup which is called "Visited link color" as color picker setting. The setting should set the color of visited link within the content area (i.e. not in the navigation areas). There isn't a pre-existing SCSS variable in Bootstrap or Moodle for that purpose unfortunately.
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 moodle-an-hochschulen/moodle-theme_boost_union, 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 moodle-an-hochschulen/moodle-theme_boost_union acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
moodle-an-hochschulen/moodle-theme_boost_union has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 20.8 places moodle-an-hochschulen/moodle-theme_boost_union in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, moodle-an-hochschulen/moodle-theme_boost_union currently has 15 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for moodle-an-hochschulen/moodle-theme_boost_union 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.