239 搜索结果 "pull requests"
拉取请求 / 使用拉取请求进行协作 / 提议更改 /
更改拉取请求的基本分支
时间表中被删除。 审查评论也可能过时,因为评论引用的代码行可能不再是拉取请求中更改的一部分。
在存储库名称下,单击
“拉取请求”。
在“Pull Requests(拉取请求)”列表中,单击要修改的拉取请求。
在拉取请求的标题旁边,单击“编辑”。
在基本分支下拉菜单中,选择要比较更改的基本分支。
阅读
REST API / 问题 /
适用于问题的 REST API 终结点
"Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the pull_request key. Be aware that the id
存储库 / 分支和合并 / 管理规则集 /
创建存储库的规则集
repository, to the right of "Always allow," click
, then click For pull requests only.
The selected actor is now required to open a pull request to make
代码安全 / 代码扫描 / 启用代码扫描 /
配置大规模代码扫描的默认设置
the repository's default branch, or any protected branch, excluding pull requests from forks.
On a weekly schedule.
For more information, see "Configuring
站点政策 / 其他站点政策 /
用户数据法律请求准则
cloning
Conversations related to Git operations such as comments on pull requests or commits
Project documentation such as Issues and Wiki pages
Statistics
GraphQL API / 参考 /
枚举
MergeQueueMergeMethod
Method to use when merging changes from queued pull requests.
MergeQueueMergeMethod 的值
MERGE
Merge commit.
REBASE
Rebase and merge
REST API / 问题 /
适用于问题被分派人的 REST API 终结点
精细令牌必须至少具有以下权限集之一:
"Issues" repository permissions (read)
"Pull requests" repository permissions (read)
如果仅请求公共资源,则无需身份验证或上述权限即可使用此终结点。
“List
GraphQL API / 参考 /
对象
object.
matchingPullRequests (PullRequestConnection)
A list of open pull requests matching the check suite.
matchingPullRequests 的参数
after (String)
Returns
迁移 / 概述 /
关于锁定的存储库
repository, such as pushing commits, creating issues, or commenting on pull requests.
Whether your repositories will be locked during migration depends on
代码安全 / Dependabot /
使用 Dependabot
Guidance and recommendations for working with Dependabot, such as managing pull requests raised by Dependabot, using GitHub Actions with Dependabot, and troubleshooting