We’re hopeful that you’ll find value in using stackd.io along with your
existing tools to manage your infrastructure. We’re also hopeful that
you’ll find ways to help contribute. Either through finding and
reporting bugs, providing new features, or even getting your hands dirty
and contributing some code or docs. However you feel comfortable
contributing, we offer a few helpful guidelines to make it that much
easier.

Note that stackd.io is built on SaltStack, and we believe that its
community will find stackd.io useful. As such, we’re trying to stay
close to the conventions and guidelines they’ve adopted to make it
easier for folks in that community to help out – and we’ve borrowed
from the SaltStack Development
guide
:)

Since we’re using Github, the recommended workflow for fixing bugs,
adding features, or modifying documentation is to fork and submit pull
requests. The process is pretty straightforward, but if you’re
unfamiliar with Github, take some time to browse through Github’s
Help.

The branch name that the pull request originates from should start with
either feature/ or bugfix/, depending on its contents. The rest
of the branch name should describe the contents of the patch, preferably
by being an Issue#. Issue#’s are required for bugfix/ branches.