If you would like to contribute to the IATI-Codelists-NonEmbedded project, you can....
- Send us feedback about your user experience. Contact details at: https://github.com/IATI
- Report bugs
- Request new features
- Contribute code, text, or documents to improve the application. See the list of specific tasks below.
If you are able to work with GitHub then please "Create an issue"
Before creating a new issue check to see if the issue already exists. If not then please do report it. If you have permissions to assign the issue to people and milestones then try to select suitable options.
If you are not comfortable working with GitHub, but would still like to contribute, then talk to us. Details at: https://github.com/IATI
- the master branch contains the latest information
- Other branches represent development work or bug fixes.
- Fork this repository (if you haven't previously)
- Make sure you're working on top of an up to date copy of IATI's master branch
- Create a branch named after the work you're doing (if you're targeting a specific issue, start the branch name with the issue number e.g.
42-feature-name
)
- Create a branch named after the work you're doing (if you're targeting a specific issue, start the branch name with the issue number e.g.
- Do your work
- If your work addresses a specific issue, reference that issue in your commit message by starting the commit message with
[#issue number]
e.g.[#64]
- If your work involves modifying a Non-Embedded Codelist, create a separate pull request to update the changelog and add a link from one to the other.
- If your work addresses a specific issue, reference that issue in your commit message by starting the commit message with
- Create a pull request
If you find any issues in deploying your own version of the code/documentation we'd love to hear about it and try to improve our deployment documentation.
We would welcome any improvements to how the code or the application is documented.
Can you improve the unit testing to make deployment more robust?
We mark some of issues as 'Bitesize'. Generally these will help ease you into the code and help you find your way around.
We'd love to hear from you. Details at: https://github.com/IATI
For general guidance on contributing to IATI Code please see http://iatistandard.org/developer/contribute/