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
- 4.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 490 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions