If you would like to upgrade to a newer long-term support version of Studio Pro, see Moving from Mendix Studio Pro 8 to 9.
Contribute to a Mendix GitHub Repository
Last modified: August 19, 2024
Introduction
We like to work with our community, and we encourage you to create and contribute using pull requests!
This how-to teaches you how to do the following:
- Contribute to a Mendix GitHub Repository according to Mendix guidelines
Prerequisites
Before starting with this how-to, make sure you have completed the following prerequisites:
- Have a GitHub account
- Have a Mendix account
- Fork a repository on GitHub (for details, see Fork a Repo)
Making Changes to an Existing Repository
To make changes to an existing repository, follow these guidelines:
- Create a new branch from where you want to base your work on your fork (this is usually the repository’s production branch)
- To quickly create a branch based on production, use
git checkout -b fix/production/my_contribution production
- Avoiding working directly on the production branch is advised
- Make commits of logical units
- Check for unnecessary whitespace with
git diff --check
before committing. - Make sure you have added the necessary tests for your changes
- Run all the tests to assure nothing was accidentally broken
Submitting Changes
To submit changes, follow these guidelines:
- Push your changes to the branch in your fork of the repository
- Submit a pull request to the appropriate repository in the Mendix organization (for more information, see About Pull Requests)
- Mention the ID’s for any issues that are fixed by the changes (for more information, see Closing Issues Using Keywords)
- After feedback has been given, Mendix expects a response within two weeks
- After two weeks, we may close the pull request if it isn’t showing any activity