Contribute your code

This document provides guidelines for contributing to the DBeaver repository. It outlines the procedures for creating pull requests, fixing bugs, and maintaining consistency in code style within our codebase.

Generally, you can suggest any feature you think is useful for the database management tool. However, we usually do not implement features that are too specific to your development process or specific to your internal company processes.

Good options include:

• Adding new database or driver support.
• Extending database metadata read/modify capabilities (e.g., adding trigger reading for a specific database).
• Adding a new SQL generator.
• Adding a new data export format.
• Localizing the DBeaver interface (extend existing localization or add a new language). For instructions, see Localization article.
• Adding a new database-specific tool (e.g., table analysis for a specific database).

You can find code examples of all these features in our codebase.

Important: When suggesting new features, be aware that if a feature already exists in the Lite, Enterprise, Ultimate, or Team Editions, we may not merge it into the Community Edition.

If you identify a bug on our board that needs fixing and it is not scheduled for the nearest milestone, you are welcome to attempt fixing it yourself. It is a good idea to ask in the ticket because some issues may not be resolved for specific reasons.

If you decide to fix the bug and submit a pull request (refer to the guidelines), the team will review it and provide feedback if necessary. If the PR is merged, the fix will be included in the next release of the DBeaver Community Edition.

For more information in releases, see DBeaver Release Cycles

Before creating a pull request, you should first create a ticket in our issue tracker. Leave a comment indicating that you intend to implement the feature or fix the bug yourself. Once the DBeaver development or QA team has responded to your comment, you may begin your work.

You can follow the standard GitHub instructions for this process. Generally, you will need to:

• Create a fork of the dbeaver/dbeaver repository.
• Create a new branch in your fork.
• Commit your changes to this branch.
• Create a pull request to the upstream repository.

Important: When committing changes in your branch, include the ticket number in the commit message like this: dbeaver/dbeaver#issue-number Initial commit for my super-duper feature. You may make any number of commits. We typically perform a squash merge before integrating changes into the main repository.

• Please avoid creating multiple pull requests for a single issue.
• Provide a detailed description of the affected functionality.
• Avoid force-pushing commits in the PR branch, as this makes reading the commit history more difficult.

• If the UI is affected, it is recommended to provide screenshots or a video demonstrating the changes made.

The main rule is to use the same code style that is already applied in a particular source file.

• Historically, several slightly different code styles exist within our codebase. If you are modifying an old file, it is best to adhere to the code style already used in that file.
• Do not reformat code or optimize imports in a file you are changing, as it makes it very difficult to review your commits due to the volume of changes.
• Utilize our automatic code style checks for pull requests. Every PR you submit to the dbeaver/dbeaver repository will be checked, and you will be able to see the report of the checklist.

IntelliJ IDEA code style can be found at: https://github.com/dbeaver/idea-rcp-launch-config-generator.

We appreciate your contributions and offer rewards for accepted pull requests. Keep contributing to improve the project and receive a reward from the team! For more details, visit Help the Beaver.