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

Merge or cut bait #71

Closed
vinniefalco opened this issue Jun 8, 2013 · 3 comments
Closed

Merge or cut bait #71

vinniefalco opened this issue Jun 8, 2013 · 3 comments

Comments

@vinniefalco
Copy link
Contributor

There are several branches that are at various levels of aging which have unmerged changes. The sources have diverged significantly and the chances of a clean merge are essentially nil. We need to figure out whether or not each branch contains important commits and then either cherry pick them and fix the conflicts, or delete the branches.

Also, it would be best for everyone to work in their own fork so we dont have to see the feature / fix branches appear in the main repository. By doing this, we will never have to delete unmerged or merged branches again (they will just accumulate in the corresponding developers' repository until dealt with).

@ghost ghost assigned JoelKatz Jun 8, 2013
@vinniefalco
Copy link
Contributor Author

I'd also like to add that GitHub's "Pull Request" web page slows down when there are more branches in the main repo.

@vinniefalco
Copy link
Contributor Author

Looks like we've made good progress trimming the dead branches. Especially now that people are working in their own forks instead of pushing feature branches directly to the main repository. We just have a little more to go!

@vinniefalco
Copy link
Contributor Author

Repositories look clean now.

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