Contentment for Umbraco - a state of happiness and satisfaction
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 100%
Response Time: 13d
First Timer Success: 100%
leekelleher/umbraco-contentment 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 leekelleher/umbraco-contentment respond to incoming external pull requests in approximately 308.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 60.0 places leekelleher/umbraco-contentment in the A tier.
The external contributor pull request merge rate for leekelleher/umbraco-contentment is 100.0%, based on public PR activity from non-core contributors.
leekelleher/umbraco-contentment currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in leekelleher/umbraco-contentment. 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/leekelleher/umbraco-contentment?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~201 hours (96% approval). Large PRs (>500 lines) take ~1482 hours (45% approval). Keep your diff compact for rapid review.
Which Contentment version are you using? 6.1.4 Which Umbraco version are you using? Be specific: e.g. 16.3.4, (not v16) 17.4.2 Bug summary Not sure if this is specific a Contentment issue or Umbraco Search need adjustments (or option to configure this for custom properties?). The API controller is pretty much similar to this: https://github.com/kjac/UmbracoSearchDemo/blob/main/src/Site/Controllers/BooksApiController.cs When I include technique or motif (Contentment data list properties), the API seems to break. Motifs Techniques Artist is a regular Content Picker, but when I makes technique facetable as well: builder.Services.Configure<FieldOptions>(options => options.Fields = [ new () { PropertyName = "year", FieldValues = FieldValues.Integers, Facetable = true, Sortable = true }, new () { PropertyName = "artist", FieldValues = FieldValues.Keywords, Facet
Which Contentment version are you using? 6.1.4 Which Umbraco version are you using? Be specific: e.g. 16.3.4, (not v16) 17.4.2 Bug summary we've noticed that content blocks index as json when used on doctypes in the block grid meaning the content isn't easily searchable using examine. Steps to reproduce we have the following setup: rich text item element doctype a summary rich text editor property. accordion item element doctype two properties, a title textstring and a summary rich text editor. accordion items datatype based on the content blocks data editor accordion element doctype this has an items property using the accordion items datatype block grid data type this allows the rich text and accordion doctypes content page doctype this uses the block grid data type with the alias contentStackBody. when content is saved, it looks like this in the index: [{"elementType":"a33adb7f-37cb-407f-884a-d871d1fe6191","key":"e64aadb9-c25b-4b20-9a5a-daa3b990acbd","value":{"title":"This is an acc
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 leekelleher/umbraco-contentment, 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 leekelleher/umbraco-contentment acknowledge new external contributions in approximately 12 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
leekelleher/umbraco-contentment 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 ~12 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 60.0 places leekelleher/umbraco-contentment in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, leekelleher/umbraco-contentment currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for leekelleher/umbraco-contentment 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.