Skip to content

swarmnyc/SWARM-Project-Guidelines

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SWARM Project Guidelines

The reasons we created this project guidelines was to smooth our development. The good guidelines can do

  • Standardizing, the same standards use on projects helps our team members can understand projects quick and reduces learning curse to join projects.
  • Automating, we created project-generating scripts to generate projects based on our standards.
  • Improving qualities, we force projects to have lint rules and test. Also, we add git pre-commit hook for projects to run lint and test to make sure projects step high qualities.

These guidelines have accelerated our development. Hence, we shared these guidelines to you. We hope them can accelerate your development as well.

Frameworks

Version Convention

we use Semantic Versioning 2.0.0 for the versioning of all our projects.

  1. MAJOR version when you make incompatible API changes.
  2. MINOR version when you add functionality in a backwards-compatible manner.
  3. PATCH version when you make backwards-compatible bug fixes.

Recommended IDE

Recommended VS Code Extensions

About

Our templates for different language projects

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published