How To Contribute Code
Whether you’ve got a bugfix, documentation update, or new feature for us, these are the steps to follow to contribute code back into the main kandan repo.
1. Get the latest code from Github
You’ll need to understand a little bit about how git and gihub work before this step (if you need an introduction guide, Github has a good one you can learn from). In simple terms, log in to github, visit the Kandan project page, and click the “fork” button to create your own copy of the repo. You will push your changes to this new repo under your own github account, and we will pull changes into the main repo from there.
For the sake of the rest of the examples in this guide, we’re going to assume your Github username is ”GITHUB_USERNAME” and use that in our examples.
Now, we want to grab the latest from this newly created repository and pull it down to your local machine. Getting the latest code from your repo is simple, just clone it:
This will give you a directory called “kandan” on your local machine with the latest checkout from your fork of the main kandan repo. Note: this is not a direct reference to the main kandan repo. When you make changes in your fork, you’ll need to let us know about it so we can pull it over….but that’s later in the process.
2. Add a remote for the main kandan repo
One thing you’ll need to do to make things easier to integrate and keep up to date in your fork is to add the main kandan repo as a remote reference. This way you can fetch the latest code from the production version and integrate it. So, here’s how to set that up:
Then, when you need to pull the latest from the main kandan repo, you just fetch and merge the master branch:
You can also use git pull upstream master if you want it all in one step.
3. Making a branch for your changes
When adding features or bug fixes, please create a separate branch for each changeset you want us to pull in, either with the issue number in the branch name or with an indication of what the feature is. To create the branch, do something like this:
1 2 3
If you’re working on an issue in the Issues list for the main kandan repo, use the naming convention “kandan-[issue-num]” for your branch name to help us keep track of what your patch actually fixes
4. Push your code and make a pull request
When you have finished making your changes, you’ll need to push up your changes to your fork so we can grab them. With them all committed, push them:
This pushes everything in that branch up. Then you can go back over to the main kandan github page and issue a pull request from there. Tell us what you want us to merge and what it does/fixes, and one of us will pick it up.
That lets us know that there’s something new from you that needs to be pulled in. We’ll review it and get back to you about it if we have any questions. Otherwise, we’ll integrate it and let you know when it’s in!
Hope this guide helps you get started in contributing to the kandan project! If you still have questions, don’t hesitate to send an email over to firstname.lastname@example.org and we’ll get back to you.