Product: PowerShell Universal
Version: 5.6.13
I am encountering an issue with the built-in Git integration in PowerShell Universal. Please note that I am likely not using the feature in the most optimal way, and I would appreciate any guidance or suggestions you may have.
I have configured the integration in Push-Only mode, with synchronization to a GitLab repository. This serves as an archive for all apps and helps track progress on my applications. As the sole user making changes, there are no concurrent edits from others.
The behavior I observe is as follows: despite setting the sync interval to 6 hours, every save action in the Admin Console (e.g., saving a dashboard or page) immediately triggers a local commit. These commits are then pushed to the remote repository.
Additionally, a system commit occurs every 6 hours.
This has resulted in approximately 6,000 commits in the repository, with about 70% consisting of single-line or minor changes (rarely exceeding a dozen lines).
Until recently, this was manageable. However, I have now integrated the Gitlab repository with Jira using a local LLM for analysis. The high volume of granular, low-impact commits makes it difficult for the LLM to accurately assess the actual scope and progress of work.
Interestingly, automatic commits appear to occur primarily for dashboards and pages, while modules, scripts, and APIs are only included in the periodic system commits.
In summary, a single daily aggregated commit would suffice for my needs, as the LLM can handle that level of granularity effectively.
Do you see any built-in solution or recommended workaround for this issue? For example:
- An option to batch commits or delay them until the sync interval.
- A toggle to disable automatic commit-on-save in Push-Only mode.
- Any configuration adjustments to reduce commit frequency.
