Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move and/or merge existing pull requests #4

Closed
joshbuker opened this issue Sep 21, 2016 · 3 comments
Closed

Move and/or merge existing pull requests #4

joshbuker opened this issue Sep 21, 2016 · 3 comments

Comments

@joshbuker
Copy link
Member

There's plenty of open pull requests on NoamB/sorcery. We can either merge them on NoamB/sorcery and then pull the commits directly onto Sorcery/sorcery, or encourage moving the PR to Sorcery/sorcery and merging there instead. If we mix and match however, there's bound to be a history conflict and the Sorcery/sorcery history would get a bit messy with merging NoamB/sorcery onto Sorcery/sorcery multiple times; so we should probably choose one of the two options and proceed with that method only.

@joshbuker joshbuker added this to the Transition to Organization milestone Sep 21, 2016
@Ch4s3
Copy link
Contributor

Ch4s3 commented Sep 22, 2016

I would be in favor of moving the ones that seem more or less ready to go.

@Ch4s3
Copy link
Contributor

Ch4s3 commented Sep 27, 2016

Lets try to keep track and close them on the other side as we move them over.

@joshbuker
Copy link
Member Author

Looks like this might solve some twitter issues: #719

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

No branches or pull requests

2 participants