Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

Add rule for branch naming in file.

  • Loading branch information...
commit 67a7d15154d9851afc0a8c24b169b88d91ba1c2f 1 parent 6092755
@blainesch blainesch authored
Showing with 1 addition and 0 deletions.
  1. +1 −0 
1 
@@ -5,6 +5,7 @@ Thank you for your interest in contributing to Lithium! This project is built by
Here's what you need to stick to in order to have the best chance of getting your code pushed to the core:
* **Integration**: all pull requests should be submitted against the [`dev`]( branch for integration testing
+ * **Branching**: create a short and meaningful branch name that starts with either `bug/` or `feature/`. A good example would be `feature/newMediaEncode` or `bug/modelFindFix`
* **Conceptual integrity**: code should conform to the goals of the framework
* **Maintainability**: code should pass existing tests, have adequate test coverage and should conform to our coding standards & QA guidelines
* **Comprehensibility**: code should be concise and expressive, and should be accompanied by new documentation as appropriate, or updates to existing docs
Please sign in to comment.
Something went wrong with that request. Please try again.