- Connie Dove
- PowerBuilder
- Thursday, 21 April 2022 03:30 PM UTC
We have just upgraded our applications from PB10 to PB2019R3 and was successfully able to get them loaded into Azure DevOps for source control. Now we are running into issues when we need to make a change to the applications. We only have 2 PB developers and each have their own applications. We are both new to GIT. Our agency is using Git and DevOps with our Visual Studio .Net applications and now our manager wants us to get our Powerbuilder code into source control following the same format as out other applications.
The developer will pull down the code to their local machine from DevOps. They will create a new branch for the changes. They will make the changes needed. They will then commit the changes. They will then push their branch up to DevOps. Then they have to do a pull request to move the changes from their branch to our QA branch. When they go to do this, they always get merge confilts, saying that the changes have been made in both. Usually one of those conflicts is the project file and the other is the windows or datawindows worked on.
Has anyone put together cheat sheets of working in this type of environment. I watched the videos from the Elevates and that is how I was able to get out code into the Repos in DevOps.
Or any guidance anyone can provide?
Thank
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.