We follow the standard GitHub fork & pull approach to pull requests.

This project now provides a LeetCode solution in two languages, and you can provide another language solution for LeetCode if you like. But to maintain a good style, your code must meet the requirements of this project.

Now myleetcode project structure is:

• myleetcode:
  • codes
  • images
  • .gitignore
  • .travis.yml
  • CONTRIBUTING.md
  • LICENSE
  • README.md
  • _config.yml

All solutions of LeetCode, must be created in package of codes.

• Class Name: Start with _, then spell problem number of LeetCode.
• Method Name: Initial in lowercase, then follow hump format.

• Python File Name: Start with _, then spell problem number of LeetCode.
• Method Name: Initial in lowercase, then spell with _, if method name have more than one word.

• Go File Name: Start with _, then spell problem number of LeetCode.
• Method Name: Initial in lowercase, then follow hump format.

• Specify commit prefix based on language, such as java:、python: and go:.