|
|
|
|
|
by PaulHoule
1060 days ago
|
|
What specifically is the problem? Using git for everything is not a bad idea because then you have consistent ids for each version and you can manage everything together. You could build something that can manage multiple versions in SQL with an approval process (particularly if the order of the rows doesn't matter) but changes there won't be synchronized with git without more trouble. Look for little things you can do to streamline the process you already have, for instance you might be able to hide the git manipulation behind some scripts if you haven't already. |
|