As I continue to research Git and PowerBuilder I am trying to understand the best setup.
1) Repository - There have been some articles saying the GIT repository name must be the same name as the workspace but when you select the 'Add to Source' it allows you to have the repository name different than the workspace. And even the 'Connect to' allows them to be different. Is this now ok to do? Should we still keep those names the same? Seems a little restrictive but if there is a reason then I will follow it.
2) PBL - To source or not to source...that is the question. I have read that the PBL should only be pushed the first time and then everything after that is just importing the changes into the PBL. What happens if you go back and forth between multiple releases? How does the PBL deal with objects being removed and added? What happens when you get the latest release the first time (ie. new developer) and you already have multiple releases out there? Our current model is we flag the PBL as a 'product' and it gets checked-in for the final release so when you go get the objects for the next release then the PBL is up-to-date. This makes it so only changes for the current release need to get imported. What is the best practice here for Git and PBLs?
3) When modifying code we always associate a task to the work when we do the check-out. Once we are done with that piece of work we check it in and sign off the task. This allows the build process to pick up just that change. Since Git does not have a Check-out/in then how do you associate changed code to a particular work item? We are always working on multiple features at the same time so I can't just have a bunch of changed code out there and not know what the change is associated to.
Thanks for any input,