Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The easiest way to contribute to swiz is to commit your changes via Git. Just create your own fork of the most recent milestone develop branch. Alternatively, you can create individual patches in Git to target specific bugs. If you've gone the route of updating a fork (recommended), all you need to do is submit a pull request via GitHub. The next step is to let us know by sending the following information to the swiz Swiz team:

  • URL for your forked repository / or Git patch
  • Detailed description of your intent
    • What did you do?
    • Why did you do it?
  • Test Cases / Unit Tests - While test cases are optional but they will assist in getting you your changes committed. If you provide unit tests, you're awesome.

...

If you've written a blog entry or recorded a presentation that you think would be helpful for the swiz Swiz community, let us know. We can add the content to the wiki, merge it into the official swiz Swiz documentation or just promote it.