Commiting to master branch

[rhoit]

I know every one is eager to commit their changes to the master branch! could every one kindly follow the following point to keep the repo clean and manageable:

• be clear what you are doing
• check your changes (commit) before pushing
• Don't ever force push that will create the chaos
• commit short description
  • clearly mention summary of changes done
  • please limit your description to 20-30 characters ( not words )
  • if you are referring to issue tag the issue no like [fix #13]
• commit long description
  • its optional but there is no harm in having it.
  • Please follow 70-75 char rule per line
• try to bundle you commit as the feature or bug fixes
• if you aren't sure how to bundle the your changes (commits). Push it into new branch and create issue for some one to look over it!

@sushilthe can you put this guideline into our github page this applies for all the repositories

[ssldhl]

Done! Check it out Contributing @ FOSS Nepal.

[rhoit]

thanx! a lot!