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

Pushing and Pulling the repo #46

Closed
mhotan opened this issue May 1, 2013 · 3 comments
Closed

Pushing and Pulling the repo #46

mhotan opened this issue May 1, 2013 · 3 comments

Comments

@mhotan
Copy link
Owner

mhotan commented May 1, 2013

Our new Git Protocol.

Note: still figuring out how to apply this to Vince

  1. Everyone will fork their own copy of the master repo of blasv/DineOn
  2. No one will push directly to blasv/DineOn
  3. instead everyone will make sure their /DineOn is up to date with blasv.
  4. Then you only push to your remote repository. This way you can deconflict with your own repository.
  5. Then when, and only when, your repository /DineOn is up to date with a SIGNIFICANT feature, COMPILES, and RUNS your ask for a pullrequest
@rocketgarden
Copy link
Contributor

I set up a duplicate repo for myself (DineOnLocal). So that's basically my "fork"

@mhotan
Copy link
Owner Author

mhotan commented May 1, 2013

You are the man.

@rocketgarden
Copy link
Contributor

So it doesn't want to let me do a pull request from an unofficial fork, so I just pushed to a separate branch and did a pull request on that.
Which, incidentally, may have been a better way to go about this anyways, but no reason to fix what isn't broken
EDIT: Yeah, it looks like I'm just gonna have to make my own special branch and pretend it's a fork

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

3 participants