Contributor

Contributing to the Project

Contributions to the project are handled separately for new features and bug fixes.

Contributor Agreement

Please agree to CONTRIBUTING.md first, submit separate PR to sign contributors.txt.

New Features

1. If an issue does not already exist for the feature, add one to the issue tracker. This allows the feature to be discussed, and eventually assigned to a particular release milestone.
2. Create a new lightweight branch in your fork of the project, which is based on the master development branch.
3. When you are ready to submit a pull request, submit the pull request using master as the base for the pull request. Provide screenshot for UI changes.

Bug Fixes

1. If an issue does not already exist for the bug, add one to the issue tracker.
2. Choose a base branch for developing a fix for the bug.
   1. Use master branch in almost all situations.
   2. If a patch is required to an existing release, an additional patch may be required in addition to a fix on the master branch. In this case you may be asked to send a matching pull-request to a specific release branch.
3. Like new features, you'll want to create a new lightweight branch in your fork of the project for bug fixes. We recommend naming the branch fix-number, where number is the issue number where the bug is reported. For example, a branch fix-1960 could be used for fixing issue #1960.

Updated texts and translations

Extracted and expanded from Release Process.

The text in the UI is fetched from the .xlf files. This means that if you add a new string it will be seen in the UI, but changed strings will require some more changes.

• English language: English.xlf files should be updated. This is not a strict requirement, but simplifies for testers and make sure that no untended strings are added to the translation strings. Please refer to Translations: how to update English translations for more details.
• All other languages: For all languages than English, the source is on Transifex, see Translations, no direct changes in Git Extensions.

Documentation

Update the documentation, or raise an Issue to indicate that documentation updates are required (see Updating the Documentation for further details).