跟进:GitHub贡献礼节，拉取请求与新发行 [英] Followup: Etiquette of GitHub Contributing, Pull Requests vs New Issue

问题描述

作为 GitHub礼仪，请求请求的后续操作VS新期刊:

向已准备好全部提取的代码提交提取请求的礼节"方式是什么?

What is the 'etiquette' way of submitting a pull request to an all-ready pulled bit of code?

考虑:

Author A - owns the repo for TowerApp.
Author B - forks TowerApp, creates a new feature - ElevatorModule, 
             then submits a pull request.    
Author A - likes the ElevatorModule pull request so he/she merges it
Author C - finds Author A's TowerApp and wants to update ElevatorMusic in 
             ElevatorModule that was recently merged from Author B's 
             pull request.

作者C做什么?

• 分叉作者B的回购并拉动请求"对作者B的更新

或

• 叉作者A的回购并拉动请求"更新作者A

推荐答案

由于 B 最终向 A 提交了拉取请求，因此 TowerApp 像主要的上游资源库.

As B eventually submitted a pull request to A, TowerApp looks like the main upstream repository.

我会分叉 A 的仓库，并在Pull Request上通知 B ，以使他保持循环.

I'd go with forking A's repo and notifying B on the Pull Request in order to keep him in the loop.

例如，

"This adds ElevatorMusic feature to @B's awesome work with the ElevatorModule"

"This adds ElevatorMusic feature to @B's awesome work with the ElevatorModule"

这将允许 B 发出提示音并查看/评论拉动请求.

This will allow B to chime in and review/comment on the pull request as well.

这篇关于跟进:GitHub贡献礼节，拉取请求与新发行的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！