Up to now, gCTS creates new commits when you release a transport request. What if that was no longer necessary? What if you could abstract a bit from the classical CTS entities? In gCTS, you currently use virtual SIDs and transport layers to determine the repository where a certain object shall be pushed to. If you work in big ABAP projects involving many modules, you will most probably rely on a central development system that is used by many developers.įor other aspects, we try to get closer to what working with Git is expected to look like. It is hard to provide it as a development environment to all developers on their own machines. For some parts, this is not easy to change.
If you´ve already taken a look at Git-Enabled Change and Transport System (gCTS), you might have found that despite all efforts, the development processes for ABAP still differ from what you might be used in other environments. !!! Please note that the repository link has changed.