Contribute and share :)
- Fork this project
- Create a new feature/patch branch
- Code code code
- run
grunt
to ensure the uglify, css minify, jshint, csslint and jscs pass - Write a good commit message with some guidelines here:
- angularjs commit message guideline with format
<type>(<scope>): <subject>
- use the present tense ("Add feature" not "Added feature")
- use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- limit the first line to 72 characters or less
- reference issues and pull requests liberally
- consider starting the commit message with an applicable emoji as inspired by atom guidelines:
- 🎨
:art:
when improving theformat
of the code - 🐎
:racehorse:
when improvingperformance
- 🚱
:non-potable_water:
when pluggingmemory
leaks - 📝
:memo:
when writingdocs
- 🐧
:penguin:
when fixing something onLinux
- 🍎
:apple:
when fixing something onMac OS
- 🏁
:checkered_flag:
when fixing something onWindows
- 🐛
:bug:
when fixing abug
- 🔥
:fire:
when removing code or files - 💚
:green_heart:
when fixing theCI
build - ✅
:white_check_mark:
when adding tests - 🔒
:lock:
when dealing withsecurity
- ⬆️
:arrow_up:
when upgradingdependencies
- ⬇️
:arrow_down:
when downgradingdependencies
- 👕
:shirt:
when removinglinter
warnings
- 🎨
- angularjs commit message guideline with format
- Pull request using the new feature/patch branch
- Ensure the Travis build passes