Startup DITA Project — unknown changes

[Bas10R]

I'm setting up a new project based on the Startup DITA Project. I'm working on a skeleton/template that other authors could use to create their own projects. To do that, I'm creating some sample files and maps, editing project-level settings to guarantee authoring consistency, modifying the OOTB CSS etc.

Since this template project will need to be shared with others, I initialized a Git repository which others will fork and clone to get on with their own projects.

While working on the template and performing basic actions, Git detects deletions or additions of some .xml files that I didn't touch at all. Since the project will be shared with other writers, I don't want to confuse them with these file changes. I assume a setting in the Startup DITA Project controls this, but I'm pretty new to framework customizations and actions, so I can't pinpoint the reason behind this and how to turn that off.

I could put the patterns I identify into the .gitignore file, but I'm not sure if those are necessary for the Startup DITA Project to function properly.

As I mentioned, sometimes, the repo detects additions or deletions of these files. I'm attaching a sample screenshot of the changes.

oxygen-actions-changes.png (28.44 KiB) Viewed 493 times

[Radu]

Hi,

We are aware of this problem.
There is an opened issue on our side to investigate things, I will paste the issue ID below for future reference:
EXM-53340 EXF automatically generates and regenerates some insertion actions
In my opinion you should commit and push the 4 generated files to the Git repository whenever they appear changed.
But even if you do not do this, nothing will break, I have the same problem with the Oxygen XML Blog and I chose not to commit them:
https://github.com/oxygenxml/blog/tree/ ... -extension

Regards,
Radu

[Bas10R]

Hi Radu,

Thank you for your reply. So if nothing breaks whether I save the files or not, I assume it's safe to put these specific folders into .gitignore, right?
I'd rather avoid authors working on the same branch commit and push these types of changes, as this might introduce unnecessary conflicts.

Regards,
Konrad

[Radu]

Hi Konrad,
Yes, I agree.
Regards,
Radu