GitHub

Get details about specific GitHub Actions resources. Use this tool to get details about individual workflows, workflow runs, jobs, and artifacts by their unique IDs.

in ▸ repo owner method resource_id

Tools for listing GitHub Actions resources. Use this tool to list workflows in a repository, or list workflow runs, jobs, and artifacts for a specific workflow or workflow run.

in ▸ page repo owner method per_page resource_id workflow_jobs_filter workflow_runs_filter

Trigger GitHub Actions workflow operations, including running, re-running, cancelling workflow runs, and deleting workflow run logs.

in ▸ ref repo owner inputs method run_id workflow_id

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

in ▸ body line path repo side owner startLine startSide pullNumber subjectType

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

in ▸ body repo owner issue_number

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

in ▸ body repo owner commentId pullNumber

Assign Copilot to a specific issue in a GitHub repository. This tool can help with the following outcomes: - a Pull Request created with source code changes to resolve the issue More information can be found at: - https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot

in ▸ repo owner base_ref issue_number custom_instructions

Create a new branch in a GitHub repository

in ▸ repo owner branch from_branch

Create a new gist

in ▸ public content filename description

Create or update a single file in a GitHub repository. If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations. In order to obtain the SHA of original file version before updating, use the following git command: git rev-parse <branch>:<path to file> SHA MUST be provided for existing file updates.

in ▸ sha path repo owner branch content message

Create a new pull request in a GitHub repository.

in ▸ base body head repo draft owner title maintainer_can_modify

Delegate a task to GitHub Copilot coding agent to perform in the background. The agent will create a pull request with the implementation. You should use this tool if the user asks to create a pull request to perform a specific task, or if the user asks Copilot to do something.

in ▸ repo owner title base_ref problem_statement

Create a new GitHub repository in your account or specified organization

in ▸ name private autoInit description organization

Delete a file from a GitHub repository

in ▸ path repo owner branch message

Dismiss a notification by marking it as read or done

in ▸ state threadID

Fork a GitHub repository to your account or specified organization

in ▸ repo owner organization

Get details of a specific code scanning alert in a GitHub repository.

in ▸ repo owner alertNumber

Get details for a commit from a GitHub repository

in ▸ sha page repo owner perPage include_diff

Get the status of a GitHub Copilot coding agent job. Use this to check if a previously submitted task has completed and to get the pull request URL once it's created. Provide the job ID (from create_pull_request_with_copilot) or pull request number (from assign_copilot_to_issue), or any pull request you want agent sessions for.

in ▸ id repo owner

This tool can be used to provide additional context to the chat from a specific Copilot space. If the user mentions the keyword 'Copilot space' with the name and owner of the space, execute this tool. The response includes a table of contents (TOC) listing all documents in the space, followed by the full content of each document. Documents are separated by markers in the format: '--- Document N: path (size) ---'. When searching for specific information, use grep (or equivalent command) to search across all documents; the separator lines will help identify which document contains the matching content.

in ▸ name owner

Get details of a specific dependabot alert in a GitHub repository.

in ▸ repo owner alertNumber

Get a specific discussion by ID

in ▸ repo owner discussionNumber

Get comments from a discussion

in ▸ repo after owner perPage discussionNumber

Get the contents of a file or directory from a GitHub repository

in ▸ ref sha path repo owner

Get gist content of a particular gist, by gist ID

in ▸ gist_id

Get a global security advisory

in ▸ ghsaId

Get logs for GitHub Actions workflow jobs. Use this tool to retrieve logs for a specific job or all failed jobs in a workflow run. For single job logs, provide job_id. For all failed jobs in a run, provide run_id with failed_only=true.

in ▸ repo owner job_id run_id tail_lines failed_only return_content

Get a specific label from a repository.

in ▸ name repo owner

Get the latest release in a GitHub repository

in ▸ repo owner

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Get detailed information for a specific GitHub notification, always call this tool when the user asks for details about a specific notification, if you don't know the ID list notifications first.

in ▸ notificationID

Get a specific release by its tag name in a GitHub repository

in ▸ tag repo owner

Get the tree structure (files and directories) of a GitHub repository at a specific ref or SHA

in ▸ repo owner tree_sha recursive path_filter

Get details of a specific secret scanning alert in a GitHub repository.

in ▸ repo owner alertNumber

Get details about a specific git tag in a GitHub repository

in ▸ tag repo owner

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

in ▸ org team_slug

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

in ▸ user

Retrieve documentation relevant to answer GitHub product and support questions. Support topics include: GitHub Actions Workflows, Authentication, GitHub Support Inquiries, Pull Request Practices, Repository Maintenance, GitHub Pages, GitHub Packages, GitHub Discussions, Copilot Spaces

in ▸ query

Get information about a specific issue in a GitHub repository.

in ▸ page repo owner method perPage issue_number

Create a new or update an existing issue in a GitHub repository.

in ▸ body repo type owner state title labels method assignees milestone duplicate_of issue_number state_reason

Perform write operations on repository labels. To set labels on issues, use the 'update_issue' tool.

in ▸ name repo color owner method new_name description

List branches in a GitHub repository

in ▸ page repo owner perPage

List code scanning alerts in a GitHub repository.

in ▸ ref repo owner state severity tool_name

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

in ▸ sha page repo owner author perPage

Retrieves the list of Copilot Spaces accessible to the user, including their names and owners.

List dependabot alerts in a GitHub repository.

in ▸ repo owner state severity

List discussion categories with their id and name, for a repository or organisation.

in ▸ repo owner

List discussions for a repository or organisation.

in ▸ repo after owner orderBy perPage category direction

List gists for a user

in ▸ page since perPage username

List global security advisories from GitHub.

in ▸ cwes type cveId ghsaId affects updated modified severity ecosystem published isWithdrawn

List supported issue types for repository owner (organization).

in ▸ owner

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

in ▸ repo after owner since state labels orderBy perPage direction

List labels from a repository

in ▸ repo owner

Lists all GitHub notifications for the authenticated user, including unread notifications, mentions, review requests, assignments, and updates on issues or pull requests. Use this tool whenever the user asks what to work on next, requests a summary of their GitHub activity, wants to see pending reviews, or needs to check for new updates or tasks. This tool is the primary way to discover actionable items, reminders, and outstanding work on GitHub. Always call this tool when asked what to work on next, what is pending, or what needs attention in GitHub.

in ▸ page repo owner since before filter perPage

List repository security advisories for a GitHub organization.

in ▸ org sort state direction

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

in ▸ base head page repo sort owner state perPage direction

List releases in a GitHub repository

in ▸ page repo owner perPage

List repository security advisories for a GitHub repository.

in ▸ repo sort owner state direction

List secret scanning alerts in a GitHub repository.

in ▸ repo owner state resolution secret_type

List starred repositories

in ▸ page sort perPage username direction

List git tags in a GitHub repository

in ▸ page repo owner perPage

Manage a notification subscription: ignore, watch, or delete a notification thread subscription.

in ▸ action notificationID

Manage a repository notification subscription: ignore, watch, or delete repository notifications subscription for the provided repository.

in ▸ repo owner action

Mark all notifications as read

in ▸ repo owner lastReadAt

Merge a pull request in a GitHub repository.

in ▸ repo owner pullNumber commit_title merge_method commit_message

Get details about specific GitHub Projects resources. Use this tool to get details about individual projects, project fields, and project items by their unique IDs.

in ▸ owner fields method item_id field_id owner_type project_number status_update_id

Tools for listing GitHub Projects resources. Use this tool to list projects for a user or organization, or list project fields and items for a specific project.

in ▸ after owner query before fields method per_page owner_type project_number

Add, update, or delete project items, or create status updates in a GitHub Project.

in ▸ body owner method status item_id item_repo item_type item_owner owner_type start_date target_date issue_number updated_field project_number pull_request_number

Get information on a specific pull request in GitHub repository.

in ▸ page repo owner method perPage pullNumber

Create and/or submit, delete review of a pull request. Available methods: - create: Create a new review of a pull request. If "event" parameter is provided, the review is submitted. If "event" is omitted, a pending review is created. - submit_pending: Submit an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. The "body" and "event" parameters are used when submitting the review. - delete_pending: Delete an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request.

in ▸ body repo event owner method commitID pullNumber

Push multiple files to a GitHub repository in a single commit

in ▸ repo files owner branch message

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

in ▸ repo owner pullNumber

Scan files, content, or recent changes for secrets such as API keys, passwords, tokens, and credentials. This tool is intended for targeted scans of specific files, snippets, or diffs provided directly as content. It accepts file contents or diffs and returns detected secrets with their locations and related secret scanning metadata. Content must not be empty. For full repository scanning, other mechanisms are available. Caveats: - Only files within the codebase should be scanned. Files outside of the codebase should not be sent. - Files listed in .gitignore should be skipped.

in ▸ repo files owner

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

in ▸ page sort order query perPage

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

in ▸ page repo sort order owner query perPage

Find GitHub organizations by name, location, or other organization metadata. Ideal for discovering companies, open source foundations, or teams.

in ▸ page sort order query perPage

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

in ▸ page repo sort order owner query perPage

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

in ▸ page sort order query perPage minimal_output

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

in ▸ page sort order query perPage

Star a GitHub repository

in ▸ repo owner

Add a sub-issue to a parent issue in a GitHub repository.

in ▸ repo owner method after_id before_id issue_number sub_issue_id replace_parent

Triage an issue by capturing a focused triage rationale and optionally applying metadata (labels, issue type, and issue fields) in a single operation. Use this tool when: - You are triaging a newly opened or untriaged issue for maintainers - You need to categorize the issue (type) and suggest/apply relevant labels - You want to record a brief, structured triage report Do not use this tool when: - The user is asking a general product question unrelated to triaging a specific issue triage_rationale should be concise markdown aimed at maintainers (not the issue author); it should contain: - Summary of the issue - Analysis of the problem or request - Suggested next steps or actions.

in ▸ repo type owner fields labels issue_number triage_rationale

Unstar a GitHub repository

in ▸ repo owner

Update an existing gist

in ▸ content gist_id filename description

Update an existing pull request in a GitHub repository.

in ▸ base body repo draft owner state title reviewers pullNumber maintainer_can_modify

Update the branch of a pull request with the latest changes from the base branch.

in ▸ repo owner pullNumber expectedHeadSha