user-activity

User Activity

Find the repositories an account owns, then retrieve a user's profile, their contributions (commits, PRs, issues, reviews), and star growth per repository.

Prerequisites

• The target GitHub username, or the owner whose repositories you want
• GitHub token with read:user scope, since most of these tools use the GraphQL API

search_user, get_user_activities and get_repo_stars_since run as long-running tasks and report progress while they work. list_repos is a plain read.

Workflow

1. Find the repository - call list_repos when you do not already know the name
2. Look up the profile - call search_user to confirm the user exists and get context
3. Retrieve contributions - call get_user_activities, optionally filtered by org, repo or date range
4. Measure star growth - call get_repo_stars_since when the question is about stars in a time window

list_repos

Parameter	Type	Default	Description
owner	str	""	User or organisation. Omit for the caller's own
sort	str	updated	One of updated, pushed, created, full_name
per_page	int	30	Results per page, 1 to 100
page	int	1	Page number

Returns {"total": int, "repos": [...]}, each entry carrying name, owner, description, default_branch, private, fork, archived, pushed_at and html_url. total counts the page returned, not everything the owner has.

You do not say whether the owner is a person or an organisation, because the tool reads the account type and picks the endpoint itself. That matters: GitHub's organisation endpoint returns 404 for a person, and its user endpoint accepts an organisation but returns only its public repositories.

Omitting owner is the only way to see private repositories you own. Passing your own username instead reads the public listing and quietly leaves them out. An organisation's private and internal repositories do appear, for a token entitled to see them.