Does Mendix Support Git‑style Merge Requests or Code Review Workflows?
0
We are currently evaluating how to improve our development workflow, especially around handling parallel development, feature branches, and merging activities. In traditional Git-based platforms like GitLab EE and GitHub, we rely heavily on Merge Requests (MRs) or Pull Requests (PRs) to review and merge changes efficiently.However, in Mendix Team Server (SVN-backed), we do not see an equivalent feature or a dedicated UI screen that supports merge request workflows directly within Team Server.I would like to request your guidance on the following:Is there any Mendix-provided feature, interface, or workflow that facilitates Merge Requests / Pull Requests similar to Git-based platforms?For example, a centralized place where team members can review diffs, comment on changes, or approve merges before they are integrated.Is there a dedicated screen or tool in Mendix Team Server to manage merges—other than manually pulling branches and merging through the Mendix Studio Pro IDE?Are there recommended best practices, tools, or extensions for managing merge flows, especially when multiple developers are working simultaneously across multiple stories or branches?Does Mendix have plans to enhance Team Server to support Git-like MR/PR features in the future, or should teams consider migrating to Git-based repositories for advanced collaboration workflows?We are looking for ways to streamline our daily merge operations and improve code review quality, so any guidance, documentation, or recommendations from your side would be greatly appreciated.
asked
Akumalli Ameer
1 answers
0
If PR/MR-style workflows are important for your team, you may want to consider moving to a Git-based repository such as Bitbucket, GitHub, or GitLab. Some Mendix teams use Bitbucket, which I recommend, specifically to get access to pull requests, code reviews, and approval workflows that are not available in Team Server.
Just keep in mind that this means managing your app in a Git setup instead of the default Team Server workflow, so it’s more of an architectural/team decision than a small tooling tweak.