3 items
Personalization and context for pull requests on GitHub & Bitbucket Reviewing pull requests is one of the most crucial interactions among developers in a team. However, there are usually too many requests to review for every developer, resulting in bad or no reviews. We try to help by prioritizing pull requests for a developer, so they can at least review the important PRs carefully. We help prioritize by adding context to the PR, like the familiarity of the reviewer with the files changed in the PR (using git commit history). Additional context can be added by integrating production events and business events (coming soon). We currently support GitHub and Bitbucket. To request support for other Git hosting services, like GitLab, Gitae, Azure repos etc., please drop us an email at contact@vibinex.com.
Sep 5, 2024
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.