đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
We propose adding branching and merging functionality to Nintex Automation on Prem (K2 Five). The goal of this feature is to allow developers to create their own branches, with the version control system creating a copy of the codebase at that point in time. Changes made in a branch should not affect the work of other developers on the team. This enables developers to work on features or bug fixes without disrupting others' progress. At a later stage, these changes can be merged back, with the platform managing the merge process and identifying conflicts to facilitate the smooth integration of changes.
Benefits:
Ensures developer independence by maintaining separate codebases for each branch.
Enhances team collaboration by allowing isolated development of changes that can later be merged.
Simplifies the merging process by detecting and addressing conflicts early on.
