Skip to content
This repository was archived by the owner on Jun 1, 2022. It is now read-only.

Github organizations #14

Open
benjaoming opened this issue May 4, 2017 · 0 comments
Open

Github organizations #14

benjaoming opened this issue May 4, 2017 · 0 comments

Comments

@benjaoming
Copy link

As a consequence of discussing the concept of "internal pull requests" in #10 (which is a concept I think should be entirely abolished because it's hardly defined), I had the following comment:

"All changes should go through Pull Requests - even owners of the repository should open Pull Requests for all their changes"

I think one consequence is that owners of a repository should always work in their own private fork in order to avoid leaving branches around in the original main repository..

@cben then commented:

Do all "open open source" projects even have a github org?
Because if you just work in $you/$repo, it will include your feature branches (at least for your active PRs) by definition.
(which is one of the reasons creating an org up front is not a bad idea. but I don't see that mentioned anywhere. is there any separate "how to make your project open open source" guidance?)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant