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

Too many branches #29

Closed
ye-luo opened this issue Feb 22, 2018 · 2 comments
Closed

Too many branches #29

ye-luo opened this issue Feb 22, 2018 · 2 comments
Labels

Comments

@ye-luo
Copy link
Collaborator

ye-luo commented Feb 22, 2018

A year ago 10 branches, now 28. This is a development process (human) bug.

We should adopt best development practices.
Every developer needs to use a fork and work under their fork.
If a feature is ready and well tested, it needs a pull request and a proper code review before merging.
The master must be protected such that no one can push directly.
A not merged feature basically doesn't exist so once done, must be merged or dropped in the developer fork.

@ye-luo ye-luo added the bug label Feb 22, 2018
@naromero77
Copy link
Collaborator

This is the workflow we use for QMCPACK development. Hopefully it is helpful to you as well.
https://github.com/QMCPACK/qmcpack/wiki/Development-workflow

@KenichiNomura
Copy link
Member

not completely cleaned up but deleted some unused branches.

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

No branches or pull requests

4 participants