search

cuneCSClub / Pandamonium

Master fork of Pandamonium
1 stars 3 forks source link

Team-specific Repositories #9

Closed blue42u closed 8 years ago

blue42u commented 8 years ago

It might be worth forking Pandamonium into 5 other repositories, under modified names. That way, each team could have a place to push to, collaborate, send messages, and finally submit a pull request to the master repository. In addition, a change in the repo-level permissions would allow the team to push to their repo, and not anyone else's. This would also mean that only one pull request would ever have to be submitted to the master repo.

The workflow would look something like this:

  1. Clone the team-specific repository.
  2. Make changes, talk with the team, commit and sync/push.
  3. Repeat step 2 until something is ready to be added to the master repo.
  4. Create a pull request from the team repo to the master repo.
  5. Profit!

I believe with my current permissions, I can create the necessary forks, if this gets decided on. (@jacobian56)

jacobian56 commented 8 years ago

This sounds good. Feel free to set this up.

Reepca commented 8 years ago

Alternatively, we could just have different branches of the same repository. It would have the same effect. The practical difference isn't much, though.

blue42u commented 8 years ago

The issue with branches is that then everyone would need push access to the master repo, and if someone pushed to the wrong branch, it could cause issues across everyone for a bit.

blue42u commented 8 years ago

Alright, the repositories have been created. If there is any reason to change to branches, then just delete the 5 new repositories. I do not know if the permissions are set appropriately, but that can be easily fixed.

blue42u commented 8 years ago

Ok, turns out I can change the permissions since I created them. They are currently set for write permission for the appropriate team. Except for Collisions because I removed myself before changing the permission from read to write. Whoops. :confounded:

jacobian56 commented 8 years ago

Question: My team just pushed changes to the master fork. How do the other forks synchronize with the updated master fork?

blue42u commented 8 years ago

Each of the other forks will need to pull in the changes, similar to a pull request (in fact, a pull request could be used).