db-load-git

To load Git changes into a 1C infobase, this automation detects changed XML and BSL files in your repository and applies them to the target database. It derives connection details from .v8-project.json or explicit parameters to sync configuration automatically.

Yes, you can partially load staged or unstaged files into a 1C database. The skill supports All, Staged, Unstaged, and Commit ranges, allowing you to apply specific Git-tracked configuration changes selectively instead of performing a full load.

The best way to preview 1C configuration changes is using the dry-run option. This validates inputs, resolves the 1C path, and simulates the partial or full load process without modifying the live infobase, ensuring safe previews of your Git changes.

You do not strictly need a .v8-project.json file to apply Git-tracked 1C configuration updates. While the skill can derive connection details from it automatically, you can also provide explicit parameters like -InfoBasePath or -InfoBaseServer for the infobase connection.

Loading 1C configuration from Git requires a specific git-config directory to correctly identify and collect changed files. Operating from this directory ensures the automation accurately resolves repository paths and validates inputs before applying updates to the target infobase.