AdvaniaGIT icon indicating copy to clipboard operation
AdvaniaGIT copied to clipboard

Modified=No through setup

Open kaspermoerch opened this issue 7 years ago • 5 comments

When running ImportFrom-ModifiedNAVtoGIT the Modfied property is removed from the exported objects.

Would it be possible to make this feature optional through setup?

kaspermoerch avatar Jan 24 '18 12:01 kaspermoerch

Sure, that would be possible. But why would you want to have objects marked as modified in your source control ?

gunnargestsson avatar Jan 24 '18 17:01 gunnargestsson

When creating a Release of our module, I would like to only include the objects that have actually been modified.

I did a Export NAV objects to GIT which means I have 5000+ objects in my repository. I did that because when I ran Import GIT Objects to NAV Environment (to simulate another developer cloning the repository) it told me to delete all the standard objects that were not in my repository.

Maybe it's my workflow that needs to be changed a bit in order to fit with AdvaniaGIT. I would like something in the lines of (when AdvaniaGIT is installed and setup):

  1. Clone the repository
  2. Build the NAV Environment
  3. Import the objects from the repository
  4. Code
  5. Export changes
  6. Commit changes

kaspermoerch avatar Jan 25 '18 08:01 kaspermoerch

I always have all objects in the Objects folder in GIT. The part that belongs to my module/solution is stored in the Deltas folder as delta files.

I have some baseBranch that has unchanged objects, master = W1, IS = IS, ... My module setup.json has that baseBranch defined in setup.json I can then build deltas in the tool. See my latest blog entry - I do that there.

gunnargestsson avatar Jan 25 '18 11:01 gunnargestsson

Do you merge the deltas back to the master branch at any point?

If I wanted to add a new feature to my module I would create a new branch for development of this feature. Given your described approach how do I apply my delta files in the feature branch after spinning up my container?

kaspermoerch avatar Jan 26 '18 09:01 kaspermoerch

That will be the feature of my next blog. My Lego method. Customer setup.json two settings baseBarnch = the unchanged CRONUS or our localization deltaBranchList = comma separated list of branches with deltas as solutions then the customer branch can also have Deltas

Build function will build these together in a single customer solution and that

gunnargestsson avatar Jan 26 '18 09:01 gunnargestsson