Followup: Etiquette of GitHub Contributing, Pull Requests vs New Issue -


as followup etiquette of github contributing, pull requests vs new issue:

what 'etiquette' way of submitting pull request all-ready pulled bit of code?

consider:

author - owns repo towerapp. author b - forks towerapp, creates new feature - elevatormodule,               submits pull request.     author - likes elevatormodule pull request he/she merges author c - finds author a's towerapp , wants update elevatormusic in               elevatormodule merged author b's               pull request. 

what author c do?

  • fork author b's repo , 'pull request' update author b

or

  • fork author a's repo , 'pull request' update author a

as b submitted pull request a, towerapp looks main upstream repository.

i'd go forking a's repo , notifying b on pull request in order keep him in loop.

as in, instance:

"this adds elevatormusic feature @b's awesome work elevatormodule"

this allow b chime in , review/comment on pull request well.


Comments

Popular posts from this blog

c# - Send Image in Json : 400 Bad request -

jquery - Fancybox - apply a function to several elements -

An easy way to program an Android keyboard layout app -