Thanks for helping to improve Cordova! This page provides a general guide on making contributions to Cordova. If you can't find something on this page, please feel free to contact the dev mailing list or ask questions on the Cordova Slack.
Before contributing to Apache Cordova, it is recommended that you join the mailing list and send a brief introduction of yourself.
If you find an issue that you would like to work on, you can ask to claim it; please leave a comment indicating your intention and a committer will assign it to you. If it is clear that an issue is not being worked on, feel free to work on it yourself (but please comment first to let the assignee know).
You can submit code by submitting a pull request at one of the Apache Github mirrors at
The workflow for creating pull requests on Github generally follows these steps:
Please include the issue ID in the title of any pull requests made to Github. For more help on Git, see the Git documentation.
However you submit code, you should always call out a reviewer to look at and merge your code. GitHub helpfully suggests possible reviewers whom you can add, or you can send a mail out to the dev mailing list with a link to the pull request.
You are responsible for testing your changes and correcting any problems before submitting a pull request. Testing includes both verifying the functionality added/touched, and running the test suites to verify there are no regressions.
When we say "run the test suites" this includes:
npm testfor JS linting
cordova-android: npm run test-build
cordova-ios: npm test
cordova-js: jake test
cordova-plugman: npm test
Please add a comment in the issue about what testing you did with your change so a committer can understand what testing was done before they merge it in.
If possible, please include tests that validate your changes and catch any future regressions. Most repositories have a
tests/ directory that includes the tests for that component.
When contributing, please start your commit messages with the the issue ID (if there is one) and relevant platform (if appropriate) followed by a description of the commit. Issue IDs on GitHub should be prefixed with
GH-, which will allow GitHub to automatically link issues and PRs.
GH-2345 android: Improved exec bridge by using strings instead of JSON GH-3456 all: Fixed plugin loading paths that start with /
You are highly encouraged to describe your git commit with enough detail for someone else to understand it. In doing so, your commit message can consist of multiple lines. However, it also is highly encouraged that the first line of your commit message not exceed 50 characters. This is because some of the tooling that sits on top of git (such as the httpd apps that let you browse the repos) assumes that the first line is top-level summary that is 50 characters or less. Thus there will be highlighting and truncating of the commit message using these assumptions and it will look weird if these assumptions are not kept. There should also be a blank line between the summary and any further description. For example, here is a good commit message:
GH-1234 Fixed the whizbang widget - added more sanity checking in the build script. - fixed the API to return the correct value in the scenario where there aren't any whizbangs present. - corrected the documentation.
As an alternate to a bullet list, you could put long text here in paragraph form, with each line wrapped at 72 chars and blank lines between paragraphs.