github-automation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

GitHub Automation via Rube MCP

通过Rube MCP实现GitHub自动化

Automate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI/CD through Composio's GitHub toolkit.

Toolkit docs: composio.dev/toolkits/github

借助Composio的GitHub工具包，自动化GitHub仓库管理、议题追踪、拉取请求工作流、分支操作及CI/CD流程。

工具包文档：composio.dev/toolkits/github

Prerequisites

前置条件

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active GitHub connection via
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
github
```
Always call
```
RUBE_SEARCH_TOOLS
```
first to get current tool schemas

必须已连接Rube MCP（需确保RUBE_SEARCH_TOOLS可用）
通过
```
RUBE_MANAGE_CONNECTIONS
```
激活GitHub连接，工具包选择
```
github
```
始终先调用
```
RUBE_SEARCH_TOOLS
```
获取当前工具的架构信息

Setup

配置步骤

Get Rube MCP: Add

https://rube.app/mcp

as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming
```
RUBE_SEARCH_TOOLS
```
responds
Call
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
github
```
If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth
Confirm connection status shows ACTIVE before running any workflows

获取Rube MCP：在客户端配置中添加

https://rube.app/mcp

作为MCP服务器。无需API密钥——只需添加端点即可使用。

确认Rube MCP可用，验证
```
RUBE_SEARCH_TOOLS
```
可正常响应
调用
```
RUBE_MANAGE_CONNECTIONS
```
并指定工具包为
```
github
```
如果连接未处于ACTIVE状态，按照返回的授权链接完成GitHub OAuth认证
在运行任何工作流之前，确认连接状态显示为ACTIVE

Core Workflows

核心工作流

1. Create and Manage Issues

1. 创建与管理议题

When to use: User wants to create, list, or manage GitHub issues

Tool sequence:

GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER

- Find target repo if unknown [Prerequisite]

```
GITHUB_LIST_REPOSITORY_ISSUES
```
- List existing issues (includes PRs) [Required]
```
GITHUB_CREATE_AN_ISSUE
```
- Create a new issue [Required]
```
GITHUB_CREATE_AN_ISSUE_COMMENT
```
- Add comments to an issue [Optional]
```
GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS
```
- Search across repos by keyword [Optional]

Key parameters:

```
owner
```
: Repository owner (username or org), case-insensitive
```
repo
```
: Repository name without .git extension
```
title
```
: Issue title (required for creation)
```
body
```
: Issue description (supports Markdown)
```
labels
```
: Array of label names
```
assignees
```
: Array of GitHub usernames
```
state
```
: 'open', 'closed', or 'all' for filtering

Pitfalls:

```
GITHUB_LIST_REPOSITORY_ISSUES
```
returns both issues AND pull requests; check
```
pull_request
```
field to distinguish
Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise
Pagination:
```
per_page
```
max 100; iterate pages until empty

适用场景：用户需要创建、列出或管理GitHub议题

工具执行顺序：

```
GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER
```
- 若目标仓库未知，先查找该仓库 [前置步骤]
```
GITHUB_LIST_REPOSITORY_ISSUES
```
- 列出现有议题（包含PR） [必填]
```
GITHUB_CREATE_AN_ISSUE
```
- 创建新议题 [必填]
```
GITHUB_CREATE_AN_ISSUE_COMMENT
```
- 为议题添加评论 [可选]
```
GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS
```
- 按关键词跨仓库搜索 [可选]

关键参数：

```
owner
```
：仓库所有者（用户名或组织），不区分大小写
```
repo
```
：仓库名称（无需带.git后缀）
```
title
```
：议题标题（创建时必填）
```
body
```
：议题描述（支持Markdown格式）
```
labels
```
：标签名称数组
```
assignees
```
：GitHub用户名数组
```
state
```
：过滤状态，可选'open'、'closed'或'all'

注意事项：

```
GITHUB_LIST_REPOSITORY_ISSUES
```
会同时返回议题和拉取请求；需检查
```
pull_request
```
字段进行区分
只有拥有推送权限的用户才能设置经办人、标签和里程碑；否则这些设置会被静默忽略
分页：
```
per_page
```
最大值为100；需循环遍历所有页面直到返回空结果

2. Manage Pull Requests

2. 管理拉取请求

When to use: User wants to create, review, or merge pull requests

Tool sequence:

```
GITHUB_FIND_PULL_REQUESTS
```
- Search and filter PRs [Required]
```
GITHUB_GET_A_PULL_REQUEST
```
- Get detailed PR info including mergeable status [Required]
```
GITHUB_LIST_PULL_REQUESTS_FILES
```
- Review changed files [Optional]
```
GITHUB_CREATE_A_PULL_REQUEST
```
- Create a new PR [Required]
```
GITHUB_CREATE_AN_ISSUE_COMMENT
```
- Post review comments [Optional]
```
GITHUB_LIST_CHECK_RUNS_FOR_A_REF
```
- Verify CI status before merge [Optional]
```
GITHUB_MERGE_A_PULL_REQUEST
```
- Merge after explicit user approval [Required]

Key parameters:

```
head
```
: Source branch with changes (must exist; for cross-repo: 'username:branch')
```
base
```
: Target branch to merge into (e.g., 'main')
```
title
```
: PR title (required unless
```
issue
```
number provided)
```
merge_method
```
: 'merge', 'squash', or 'rebase'
```
state
```
: 'open', 'closed', or 'all'

Pitfalls:

```
GITHUB_CREATE_A_PULL_REQUEST
```
fails with 422 if base/head are invalid, identical, or already merged
```
GITHUB_MERGE_A_PULL_REQUEST
```
can be rejected if PR is draft, closed, or branch protection applies
Always verify mergeable status with
```
GITHUB_GET_A_PULL_REQUEST
```
immediately before merging
Require explicit user confirmation before calling MERGE

适用场景：用户需要创建、审核或合并拉取请求

工具执行顺序：

```
GITHUB_FIND_PULL_REQUESTS
```
- 搜索并过滤PR [必填]
```
GITHUB_GET_A_PULL_REQUEST
```
- 获取PR详细信息，包括可合并状态 [必填]
```
GITHUB_LIST_PULL_REQUESTS_FILES
```
- 查看变更文件 [可选]
```
GITHUB_CREATE_A_PULL_REQUEST
```
- 创建新PR [必填]
```
GITHUB_CREATE_AN_ISSUE_COMMENT
```
- 发布审核评论 [可选]
```
GITHUB_LIST_CHECK_RUNS_FOR_A_REF
```
- 合并前验证CI状态 [可选]
```
GITHUB_MERGE_A_PULL_REQUEST
```
- 获得用户明确批准后执行合并 [必填]

关键参数：

```
head
```
：包含变更的源分支（必须存在；跨仓库时格式为'username:branch'）
```
base
```
：要合并到的目标分支（例如'main'）
```
title
```
：PR标题（除非提供
```
issue
```
编号，否则必填）
```
merge_method
```
：合并方式，可选'merge'、'squash'或'rebase'
```
state
```
：状态，可选'open'、'closed'或'all'

注意事项：

如果base/head分支无效、相同或已合并，
```
GITHUB_CREATE_A_PULL_REQUEST
```
会返回422错误
如果PR是草稿状态、已关闭或存在分支保护规则，
```
GITHUB_MERGE_A_PULL_REQUEST
```
会被拒绝
合并前必须立即调用
```
GITHUB_GET_A_PULL_REQUEST
```
验证可合并状态
调用MERGE前必须获得用户的明确确认

3. Manage Repositories and Branches

3. 管理仓库与分支

When to use: User wants to create repos, manage branches, or update repo settings

Tool sequence:

GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER

- List user's repos [Required]

```
GITHUB_GET_A_REPOSITORY
```
- Get detailed repo info [Optional]

GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER

- Create personal repo [Required]

GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY

- Create org repo [Alternative]

```
GITHUB_LIST_BRANCHES
```
- List branches [Required]
```
GITHUB_CREATE_A_REFERENCE
```
- Create new branch from SHA [Required]
```
GITHUB_UPDATE_A_REPOSITORY
```
- Update repo settings [Optional]

Key parameters:

```
name
```
: Repository name
```
private
```
: Boolean for visibility
```
ref
```
: Full reference path (e.g., 'refs/heads/new-branch')
```
sha
```
: Commit SHA to point the new reference to
```
default_branch
```
: Default branch name

Pitfalls:

GITHUB_CREATE_A_REFERENCE

only creates NEW references; use

GITHUB_UPDATE_A_REFERENCE

for existing ones

```
ref
```
must start with 'refs/' and contain at least two slashes
```
GITHUB_LIST_BRANCHES
```
paginates via
```
page
```
/
```
per_page
```
; iterate until empty page
```
GITHUB_DELETE_A_REPOSITORY
```
is permanent and irreversible; requires admin privileges

适用场景：用户需要创建仓库、管理分支或更新仓库设置

工具执行顺序：

GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER

- 列出用户的仓库 [必填]

```
GITHUB_GET_A_REPOSITORY
```
- 获取仓库详细信息 [可选]

GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER

- 创建个人仓库 [必填]

GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY

- 创建组织仓库 [替代选项]

```
GITHUB_LIST_BRANCHES
```
- 列出分支 [必填]
```
GITHUB_CREATE_A_REFERENCE
```
- 基于SHA创建新分支 [必填]
```
GITHUB_UPDATE_A_REPOSITORY
```
- 更新仓库设置 [可选]

关键参数：

```
name
```
：仓库名称
```
private
```
：可见性布尔值
```
ref
```
：完整引用路径（例如'refs/heads/new-branch'）
```
sha
```
：新引用指向的提交SHA值
```
default_branch
```
：默认分支名称

注意事项：

GITHUB_CREATE_A_REFERENCE

仅用于创建新引用；现有引用需使用

GITHUB_UPDATE_A_REFERENCE

```
ref
```
必须以'refs/'开头，且至少包含两个斜杠
```
GITHUB_LIST_BRANCHES
```
通过
```
page
```
/
```
per_page
```
实现分页；需循环遍历直到返回空页面
```
GITHUB_DELETE_A_REPOSITORY
```
操作永久且不可撤销；需要管理员权限

4. Search Code and Commits

4. 搜索代码与提交记录

When to use: User wants to find code, files, or commits across repositories

Tool sequence:

```
GITHUB_SEARCH_CODE
```
- Search file contents and paths [Required]
```
GITHUB_SEARCH_CODE_ALL_PAGES
```
- Multi-page code search [Alternative]
```
GITHUB_SEARCH_COMMITS_BY_AUTHOR
```
- Search commits by author/date/org [Required]
```
GITHUB_LIST_COMMITS
```
- List commits for a specific repo [Alternative]
```
GITHUB_GET_A_COMMIT
```
- Get detailed commit info [Optional]
```
GITHUB_GET_REPOSITORY_CONTENT
```
- Get file content [Optional]

Key parameters:

: Search query with qualifiers (

language:python

repo:owner/repo

extension:js

)

```
owner
```
/
```
repo
```
: For repo-specific commit listing
```
author
```
: Filter by commit author
```
since
```
/
```
until
```
: ISO 8601 date range for commits

Pitfalls:

Code search only indexes files under 384KB on default branch
Maximum 1000 results returned from code search
```
GITHUB_SEARCH_COMMITS_BY_AUTHOR
```
requires keywords in addition to qualifiers; qualifier-only queries are not allowed
```
GITHUB_LIST_COMMITS
```
returns 409 on empty repos

适用场景：用户需要跨仓库查找代码、文件或提交记录

工具执行顺序：

```
GITHUB_SEARCH_CODE
```
- 搜索文件内容和路径 [必填]
```
GITHUB_SEARCH_CODE_ALL_PAGES
```
- 多页面代码搜索 [替代选项]
```
GITHUB_SEARCH_COMMITS_BY_AUTHOR
```
- 按作者/日期/组织搜索提交记录 [必填]
```
GITHUB_LIST_COMMITS
```
- 列出指定仓库的提交记录 [替代选项]
```
GITHUB_GET_A_COMMIT
```
- 获取提交记录详细信息 [可选]
```
GITHUB_GET_REPOSITORY_CONTENT
```
- 获取文件内容 [可选]

关键参数：

```
q
```
：带限定符的搜索查询（例如
```
language:python
```
、
```
repo:owner/repo
```
、
```
extension:js
```
）
```
owner
```
/
```
repo
```
：用于指定仓库的提交记录查询
```
author
```
：按提交作者过滤
```
since
```
/
```
until
```
：提交记录的ISO 8601格式日期范围

注意事项：

代码搜索仅索引默认分支中小于384KB的文件
代码搜索最多返回1000条结果
```
GITHUB_SEARCH_COMMITS_BY_AUTHOR
```
要求查询中除限定符外还需包含关键词；仅使用限定符的查询不被允许
空仓库调用
```
GITHUB_LIST_COMMITS
```
会返回409错误

5. Manage CI/CD and Deployments

5. 管理CI/CD与部署

When to use: User wants to view workflows, check CI status, or manage deployments

Tool sequence:

```
GITHUB_LIST_REPOSITORY_WORKFLOWS
```
- List GitHub Actions workflows [Required]
```
GITHUB_GET_A_WORKFLOW
```
- Get workflow details by ID or filename [Optional]
```
GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT
```
- Manually trigger a workflow [Required]
```
GITHUB_LIST_CHECK_RUNS_FOR_A_REF
```
- Check CI status for a commit/branch [Required]
```
GITHUB_LIST_DEPLOYMENTS
```
- List deployments [Optional]
```
GITHUB_GET_A_DEPLOYMENT_STATUS
```
- Get deployment status [Optional]

Key parameters:

```
workflow_id
```
: Numeric ID or filename (e.g., 'ci.yml')
```
ref
```
: Git reference (branch/tag) for workflow dispatch
```
inputs
```
: JSON string of workflow inputs matching
```
on.workflow_dispatch.inputs
```
```
environment
```
: Filter deployments by environment name

Pitfalls:

GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT

requires the workflow to have

workflow_dispatch

trigger configured

Full path
```
.github/workflows/main.yml
```
is auto-stripped to just
```
main.yml
```
Inputs max 10 key-value pairs; must match workflow's
```
on.workflow_dispatch.inputs
```
definitions

适用场景：用户需要查看工作流、检查CI状态或管理部署

工具执行顺序：

```
GITHUB_LIST_REPOSITORY_WORKFLOWS
```
- 列出GitHub Actions工作流 [必填]
```
GITHUB_GET_A_WORKFLOW
```
- 通过ID或文件名获取工作流详情 [可选]
```
GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT
```
- 手动触发工作流 [必填]
```
GITHUB_LIST_CHECK_RUNS_FOR_A_REF
```
- 检查提交/分支的CI状态 [必填]
```
GITHUB_LIST_DEPLOYMENTS
```
- 列出部署记录 [可选]
```
GITHUB_GET_A_DEPLOYMENT_STATUS
```
- 获取部署状态 [可选]

关键参数：

```
workflow_id
```
：数字ID或文件名（例如'ci.yml'）
```
ref
```
：用于触发工作流的Git引用（分支/标签）
```
inputs
```
：符合
```
on.workflow_dispatch.inputs
```
定义的工作流输入JSON字符串
```
environment
```
：按环境名称过滤部署记录

注意事项：

GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT

要求工作流已配置

workflow_dispatch

触发器

完整路径
```
.github/workflows/main.yml
```
会自动简化为
```
main.yml
```
输入参数最多支持10个键值对；必须与工作流
```
on.workflow_dispatch.inputs
```
定义匹配

6. Manage Users and Permissions

6. 管理用户与权限

When to use: User wants to check collaborators, permissions, or branch protection

Tool sequence:

```
GITHUB_LIST_REPOSITORY_COLLABORATORS
```
- List repo collaborators [Required]

GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER

- Check specific user's access [Optional]

```
GITHUB_GET_BRANCH_PROTECTION
```
- Inspect branch protection rules [Required]
```
GITHUB_UPDATE_BRANCH_PROTECTION
```
- Update protection settings [Optional]
```
GITHUB_ADD_A_REPOSITORY_COLLABORATOR
```
- Add/update collaborator [Optional]

Key parameters:

```
affiliation
```
: 'outside', 'direct', or 'all' for collaborator filtering
```
permission
```
: Filter by 'pull', 'triage', 'push', 'maintain', 'admin'
```
branch
```
: Branch name for protection rules
```
enforce_admins
```
: Whether protection applies to admins

Pitfalls:

```
GITHUB_GET_BRANCH_PROTECTION
```
returns 404 for unprotected branches; treat as no protection rules
Determine push ability from
```
permissions.push
```
or
```
role_name
```
, not display labels
```
GITHUB_LIST_REPOSITORY_COLLABORATORS
```
paginates; iterate all pages

GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER

may be inconclusive for non-collaborators

适用场景：用户需要查看协作者、权限或分支保护规则

工具执行顺序：

```
GITHUB_LIST_REPOSITORY_COLLABORATORS
```
- 列出仓库协作者 [必填]

GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER

- 检查特定用户的访问权限 [可选]

```
GITHUB_GET_BRANCH_PROTECTION
```
- 查看分支保护规则 [必填]
```
GITHUB_UPDATE_BRANCH_PROTECTION
```
- 更新保护设置 [可选]
```
GITHUB_ADD_A_REPOSITORY_COLLABORATOR
```
- 添加/更新协作者 [可选]

关键参数：

```
affiliation
```
：协作者过滤选项，可选'outside'、'direct'或'all'
```
permission
```
：按权限过滤，可选'pull'、'triage'、'push'、'maintain'、'admin'
```
branch
```
：保护规则对应的分支名称
```
enforce_admins
```
：保护规则是否适用于管理员

注意事项：

未受保护的分支调用
```
GITHUB_GET_BRANCH_PROTECTION
```
会返回404；需视为无保护规则
通过
```
permissions.push
```
或
```
role_name
```
判断推送权限，而非显示标签
```
GITHUB_LIST_REPOSITORY_COLLABORATORS
```
支持分页；需遍历所有页面
非协作者调用
```
GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER
```
可能返回不确定结果

Common Patterns

通用模式

ID Resolution

ID解析

Repo name -> owner/repo:

GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER

PR number -> PR details:

GITHUB_FIND_PULL_REQUESTS

then

GITHUB_GET_A_PULL_REQUEST

Branch name -> SHA:
```
GITHUB_GET_A_BRANCH
```
Workflow name -> ID:
```
GITHUB_LIST_REPOSITORY_WORKFLOWS
```

仓库名称 -> owner/repo：使用

GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER

PR编号 -> PR详情：先调用

GITHUB_FIND_PULL_REQUESTS

再调用

GITHUB_GET_A_PULL_REQUEST

分支名称 -> SHA：使用
```
GITHUB_GET_A_BRANCH
```
工作流名称 -> ID：使用
```
GITHUB_LIST_REPOSITORY_WORKFLOWS
```

Pagination

分页处理

All list endpoints use page-based pagination:

```
page
```
: Page number (starts at 1)
```
per_page
```
: Results per page (max 100)
Iterate until response returns fewer results than
```
per_page
```

所有列表端点均基于页码分页：

```
page
```
：页码（从1开始）
```
per_page
```
：每页结果数（最大值100）
循环遍历直到返回结果数少于
```
per_page
```

Safety

安全规范

Always verify PR mergeable status before merge
Require explicit user confirmation for destructive operations (merge, delete)
Check CI status with
```
GITHUB_LIST_CHECK_RUNS_FOR_A_REF
```
before merging

合并前必须验证PR的可合并状态
破坏性操作（合并、删除）需获得用户明确确认
合并前调用
```
GITHUB_LIST_CHECK_RUNS_FOR_A_REF
```
检查CI状态

Known Pitfalls

常见问题

Issues vs PRs:

GITHUB_LIST_REPOSITORY_ISSUES

returns both; check

pull_request

field

Pagination limits:
```
per_page
```
max 100; always iterate pages until empty
Branch creation:
```
GITHUB_CREATE_A_REFERENCE
```
fails with 422 if reference already exists
Merge guards: Merge can fail due to branch protection, failing checks, or draft status
Code search limits: Only files <384KB on default branch; max 1000 results
Commit search: Requires search text keywords alongside qualifiers
Destructive actions: Repo deletion is irreversible; merge cannot be undone
Silent permission drops: Labels, assignees, milestones silently dropped without push access

议题与PR区分：
```
GITHUB_LIST_REPOSITORY_ISSUES
```
会同时返回两者；需检查
```
pull_request
```
字段
分页限制：
```
per_page
```
最大值为100；必须遍历所有页面直到返回空结果
分支创建：若引用已存在，
```
GITHUB_CREATE_A_REFERENCE
```
会返回422错误
合并限制：分支保护规则、CI失败或草稿状态会导致合并失败
代码搜索限制：仅索引默认分支中小于384KB的文件；最多返回1000条结果
提交记录搜索：查询中除限定符外必须包含关键词
破坏性操作：仓库删除不可撤销；合并操作无法回滚
权限静默失效：无推送权限时，标签、经办人、里程碑设置会被静默忽略

Quick Reference

快速参考

Task	Tool Slug	Key Params
List repos	`GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`	`type` , `sort` , `per_page`
Get repo	`GITHUB_GET_A_REPOSITORY`	`owner` , `repo`
Create issue	`GITHUB_CREATE_AN_ISSUE`	`owner` , `repo` , `title` , `body`
List issues	`GITHUB_LIST_REPOSITORY_ISSUES`	`owner` , `repo` , `state`
Find PRs	`GITHUB_FIND_PULL_REQUESTS`	`repo` , `state` , `author`
Create PR	`GITHUB_CREATE_A_PULL_REQUEST`	`owner` , `repo` , `head` , `base` , `title`
Merge PR	`GITHUB_MERGE_A_PULL_REQUEST`	`owner` , `repo` , `pull_number` , `merge_method`
List branches	`GITHUB_LIST_BRANCHES`	`owner` , `repo`
Create branch	`GITHUB_CREATE_A_REFERENCE`	`owner` , `repo` , `ref` , `sha`
Search code	`GITHUB_SEARCH_CODE`	`q`
List commits	`GITHUB_LIST_COMMITS`	`owner` , `repo` , `author` , `since`
Search commits	`GITHUB_SEARCH_COMMITS_BY_AUTHOR`	`q`
List workflows	`GITHUB_LIST_REPOSITORY_WORKFLOWS`	`owner` , `repo`
Trigger workflow	`GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT`	`owner` , `repo` , `workflow_id` , `ref`
Check CI	`GITHUB_LIST_CHECK_RUNS_FOR_A_REF`	`owner` , `repo` , ref
List collaborators	`GITHUB_LIST_REPOSITORY_COLLABORATORS`	`owner` , `repo`
Branch protection	`GITHUB_GET_BRANCH_PROTECTION`	`owner` , `repo` , `branch`

Powered by Composio

任务	工具标识	关键参数
列出仓库	`GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`	`type` , `sort` , `per_page`
获取仓库信息	`GITHUB_GET_A_REPOSITORY`	`owner` , `repo`
创建议题	`GITHUB_CREATE_AN_ISSUE`	`owner` , `repo` , `title` , `body`
列出议题	`GITHUB_LIST_REPOSITORY_ISSUES`	`owner` , `repo` , `state`
查找PR	`GITHUB_FIND_PULL_REQUESTS`	`repo` , `state` , `author`
创建PR	`GITHUB_CREATE_A_PULL_REQUEST`	`owner` , `repo` , `head` , `base` , `title`
合并PR	`GITHUB_MERGE_A_PULL_REQUEST`	`owner` , `repo` , `pull_number` , `merge_method`
列出分支	`GITHUB_LIST_BRANCHES`	`owner` , `repo`
创建分支	`GITHUB_CREATE_A_REFERENCE`	`owner` , `repo` , `ref` , `sha`
搜索代码	`GITHUB_SEARCH_CODE`	`q`
列出提交记录	`GITHUB_LIST_COMMITS`	`owner` , `repo` , `author` , `since`
搜索提交记录	`GITHUB_SEARCH_COMMITS_BY_AUTHOR`	`q`
列出工作流	`GITHUB_LIST_REPOSITORY_WORKFLOWS`	`owner` , `repo`
触发工作流	`GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT`	`owner` , `repo` , `workflow_id` , `ref`
检查CI状态	`GITHUB_LIST_CHECK_RUNS_FOR_A_REF`	`owner` , `repo` , ref
列出协作者	`GITHUB_LIST_REPOSITORY_COLLABORATORS`	`owner` , `repo`
分支保护规则	`GITHUB_GET_BRANCH_PROTECTION`	`owner` , `repo` , `branch`

由 Composio 提供支持