Updated Development Process & Standards (markdown)
parent
4fd5d301c2
commit
39c6d8d88b
1 changed files with 1 additions and 1 deletions
|
@ -13,7 +13,7 @@
|
||||||
# Code Standards
|
# Code Standards
|
||||||
|
|
||||||
1. Every commit in master should work and pass tests/linting
|
1. Every commit in master should work and pass tests/linting
|
||||||
2. See [Branching-and-Merging](https://github.com/lbryio/lbry/wiki/Branching-and-Merging) for how to git
|
2. See [Branching and Merging](https://github.com/lbryio/lbry/wiki/Branching-and-Merging) for how to git
|
||||||
3. Commit messages should be informative, usable for release notes, and provide context/explanation for the change being made
|
3. Commit messages should be informative, usable for release notes, and provide context/explanation for the change being made
|
||||||
4. Commits on master should stand-alone
|
4. Commits on master should stand-alone
|
||||||
5. Force pushes on feature branches are allowed; please commit early and often, but clean-up the mess before merging into master.
|
5. Force pushes on feature branches are allowed; please commit early and often, but clean-up the mess before merging into master.
|
||||||
|
|
Loading…
Reference in a new issue