Developing on branch and merging to trunk?
Comments
-
Hello, I was wondering about best development practices. I am having an issue where when I get an ok to push something to production I am always in the process of doing another ticket for the same project or there are tickets for that project that has yet to go through QA. So if i want to push something all of the stuff that has yet to go through QA gets pushed out as well. I know in normal development you would create a branch of the code base, do your development, and when it is time you merge the branch to trunk and then push trunk to production. We have two people who develop in Decisions and we may be working on the same project at the same time so we would want to merge both to trunk and be able to check for conflicts. Is anything like that available in Decisions and if not what the best practice for this situation would be.
Howdy, Stranger!
Categories
- 2.1K All Categories
- 18 General
- 155 Installation / Setup
- 991 Flows
- 86 Rules
- 203 Administration
- 204 Portal
- 433 General Q & A
- 600 Forms
- 282 Reports
- 3 Designer Extensions
- 38 Example Flows
- 32 CSS Examples
- 1 Diagram Tile
- 5 Javascript Controls
- 139 Pages
- 1 Process Mining
- New Features
- 150 Datastructures
- 50 Repository
- 169 Integrations
- 25 Multi-Tenant
- 21 SDK
- 40 Modules
- 38 Settings
- 20 Active Directory
- 12 Version 7
- 34 Version 8