1c-db-load-git

To load changed 1C configuration files from Git, this skill detects modified XML objects and performs a partial configuration load into the target infobase, updating the database without requiring a full rebuild.

When applying Git changes to a 1C infobase, you can select from multiple change scopes including All, Staged, Unstaged, and Commit, allowing precise control over which repository modifications are loaded into the database.

Loading Git changes into a 1C database requires Git installed, a runnable runner like PowerShell or Python, a valid config directory containing XML objects, and either a local infobase path or a server reference.

Yes, you can update a 1C database from repository changes without a full rebuild by using partial configuration loads that map and apply only the touched XML objects directly to the target infobase.

Automating the load of Git changes into a 1C database reduces manual synchronization efforts by detecting changed configuration files and mapping them to the corresponding XML objects for targeted database updates.