Contributing

Contributions of every kind are welcome — bug reports, feature requests, documentation fixes, translations and code. You don't need to write a line of code to make the module better: a well-described issue is often the most valuable contribution of all.

Start with an issue

Whatever you'd like to see changed, please describe it in the issue queue first — the problem you hit, the steps to reproduce it, or the workflow a new feature should support.

The module is in active development and the code moves quickly, so a patch written against today's code may not apply next month — but a clear description of the problem or the need stays useful no matter how the code changes underneath it. It lets maintainers confirm the direction before anyone invests time in an implementation, and it gives the eventual change a place to be discussed and tested.

A good issue includes:

• For bugs — what you did, what you expected, what happened instead, and the versions involved (module release or branch, Drupal core, and for browser issues the browser/admin theme). Screenshots or console errors help a lot.
• For features — the editorial or site-building problem you're trying to solve, not just the solution you have in mind. Knowing the why often leads to a better how.

Contributing code

Code contributions are gladly accepted — please submit them as merge requests on the issue's fork at git.drupalcode.org, rather than patch files. Merge requests run the project's automated tests and coding-standards checks, stay rebaseable as the code evolves, and are much easier to review and iterate on.

The usual flow:

1. Open (or find) the issue describing the change.
2. Use Get push access on the issue to create an issue fork.
3. Create a branch from the target branch (see below), commit your change, and open a merge request.
4. Set the issue status to Needs review.

Drupal.org's contributor guide covers the mechanics in detail if this is your first contribution.

Supported branches

Branch	Status	What lands there
3.0.x	Supported, in active development	New features, bug fixes — target this branch for merge requests.
2.x	Important fixes only	Security fixes and critical bugs. No new features.

Unless an issue explicitly targets 2.x, write your merge request against 3.0.x. Fixes that also affect 2.x can be backported after they land.

Not sure where to start?

Reviewing and testing other people's merge requests is a great first contribution — every issue in Needs review needs someone to try it out and report back.