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

Enforce Git Strict Flow and GitHub Project Guidelines and define them in the readme #222

Open
JonDevOps opened this issue Jun 2, 2019 · 0 comments

Comments

@JonDevOps
Copy link
Member

https://gist.github.com/rsp/057481db4dbd999bb7077f211f53f212

no one should be able to commit code directly to the master branch (or develop, or whatever your main development branch is called) and the only way to update it should be with pull requests.

Pull requests should require at least one positive review and CI tests passing (using Travis, Circle CI etc.) before anyone can merge them. If someone’s code breaks the test, this person has to fix the PR. If the PR gets negative review, no one can merge it before it gets improved to get a positive review.

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

1 participant