Hey all, new Appian developer here! From what I have learned so far, Appian dev teams don't usually follow the branch->merge workflow, but rather work inside the single dev environment. I have no problems with this system and think it is the ideal approach for 99% of cases. However, in a situation like a refactor, where you are changing some of the architecture and breaking a few parts of the system as a side effect, I can see how branching off to make these changes would be safer, cleaner, and not prohibit other developers who need to use the parts that are being changed.Is there any version control (or hacky workaround) that could solve this in these rare situations? Thanks!
Discussion posts and replies are publicly visible
We're doing a half-way version with Azure Dev Ops pipelines which sticks items in repo. Problems occur though if attempting to get back to point in time because of recordtypes / database and service dependencies / and pull request per user story became a nightmare with some items passing testing but not all, etc.