The issue tracker is the preferred channel for bug reports, features requests and pull requests.
A bug is a demonstrable problem that is caused by the code in the repository. Good bug reports are extremely helpful - thank you!
Fork the project, clone your fork, and configure the remotes:
# Clone your fork of the repo into the current directory
git clone https://github.com/<your-username>/bibstuff
# Navigate to the newly cloned directory
cd bibstuff
# Assign the original repo to a remote called "upstream"
git remote add upstream https://github.com/dschwilk/bibstuff
If you cloned a while ago, get the latest changes from upstream:
git checkout <dev-branch>
git pull upstream <dev-branch>
Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:
git checkout -b <topic-branch-name>
Commit your changes in logical chunks. Use Git’s interactive rebase feature to tidy up your commits before making them public. The commit message should conform to the description at http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
Test your code, add tests to the /tests folder
Locally merge (or rebase) the upstream development branch into your topic branch:
git pull [--rebase] upstream <dev-branch>
Push your topic branch up to your fork:
git push origin <topic-branch-name>
Open a Pull Request with a clear title and description.