Skip to content

gilborty/sml

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1,120 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

How to contribute

Contributions are always very much appreciated. However, to make sure the process of accepting patches goes smoothly for everyone (especially for the maintainer), you should try to follow these few simple guidelines when you contribute:

  1. Fork the repository.
  2. Create a new branch based on the master branch (git checkout -b your_branch master).
  3. Do your modifications on that branch.
  4. Be sure your modifications include:
  • Don't break anything (make)
  • Proper unit/functional tests (make test)
  • Documentation updates if required (make doc)
  • Regenerate preprocessed headers (tools/pph.sh)
  • Update/check style using (make check)
  • Verify performance (make benchmarks)
  1. Commit your changes. Your commit message should reflect your changes.
  2. Push the changes to your fork (git push origin your_branch).
  3. Rebase if necessary to avoid broken commits (git rebase -i origin/master).
  4. Open a pull request against SML's master branch. I will do my best to respond in a timely manner. I might discuss your patch and suggest some modifications, or I might amend your patch myself and ask you for feedback. You will always be given proper credit.

About

SML: C++14 State Machine Library

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 44.1%
  • CSS 24.5%
  • HTML 13.7%
  • C++ 9.1%
  • SCSS 8.1%
  • CMake 0.2%
  • Other 0.3%