---
title: "Track GitHub mentions of your brand | Mentio"
description: "Issues and pull requests across public repositories that name your product, your SDK or your API, so the bug report filed in someone else's repo reaches your team."
canonical: https://mentio.dev/github/
markdown: https://mentio.dev/github/index.md
last-updated: 2026-09-23T16:19:37.703Z
---

# Track GitHub mentions of your brand | Mentio

> Issues and pull requests across public repositories that name your product, your SDK or your API, so the bug report filed in someone else's repo reaches your team.

Source: https://mentio.dev/github/

GitHub

# Track GitHub mentions of your brand

Issues and pull requests across public repositories that name your product, your SDK or your API, so the bug report filed in someone else's repo reaches your team.

[Start tracking GitHub ›](https://app.mentio.dev/login?mode=signup)[Read the docs ›](https://docs.mentio.dev)

Every 15 minutesIssues and pull requestsThe GitHub search API

## Exactly what you get, no marketing numbers

Developers file issues where they are, not where you are. An integration bug reported in a customer's repository is the earliest signal you will get.

What we watch

### Issues and pull requests

Titles and bodies of public issues and PRs that contain your keyword, with the repository and the author.

How often

### Every 15 minutes

Each keyword is searched four times an hour. GitHub's own search index surfaces an issue 15 to 50 minutes after it is opened, and the poll accounts for that lag.

Where it comes from

### The GitHub search API

The official issues search, with a token so the rate limit is generous. Nothing is scraped.

## GitHub mentions, as Mentio delivers them

Every match is scored 0 to 100 for relevance against your company context, tagged with sentiment and intent, and summarised in a line. The same shape reaches Slack, a webhook, the API and your agent.

An illustrative mention for a fictional brand, acme.

acme

2m ago

Rrachel-krachel-k/infra-tools · issue #212340 stars

acme webhook retries hit us twice for the same delivery id after a 5xx. Anyone else seeing duplicate events? Adding idempotency on our side for now.

93

A customer working around a suspected bug in your product, in public.

negativecomplaintquestionrel 93

## From post to signal in three steps

01

### Track keywords

Your brand, your competitors, your space. One POST per term, or a click in the dashboard.

02

### The pipeline watches everything

Every source is ingested once, matched against your terms, and classified by AI: relevance 0 to 100, sentiment, and intent, tuned by your company context.

03

### Act on what matters

Triage in the dashboard, deliver to Slack or webhooks, query the REST API, or let your AI agent work the feed over MCP.

Also watched, in the same feed

[X](/x/)[Reddit](/reddit/)[Hacker News](/hacker-news/)[Bluesky](/bluesky/)[LinkedIn](/linkedin/)[Stack Overflow](/stack-overflow/)[DEV](/dev/)[YouTube](/youtube/)[News](/news/)

## Start monitoring brand mentions

One request tracks your first keyword. The first scored mention lands within minutes, in Slack, a webhook, or your agent.

[Get your API key ›](https://app.mentio.dev/login?mode=signup)[Read the docs ›](https://docs.mentio.dev)

$5.80 free credit · no card · no subscription