First commit

Author: AndreaV-Lsi

CHANGELOG.md

@@ -0,0 +1,95 @@
+# Changelog
+
+All notable changes to LsiGitCheckout will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [2.1.2] - 2025-01-10
+
+### Removed
+- Removed dead code: Get-SshKeyPassword function (not used with PuTTY/Pageant)
+
+### Fixed
+- Script structure syntax errors
+
+## [2.1.0] - 2025-01-10
+
+### Changed
+- **BREAKING**: Removed OpenSSH support - now PuTTY/plink only
+- Simplified SSH key handling to only support PuTTY format (.ppk)
+- Removed -SshClient parameter
+
+### Removed
+- All OpenSSH-related code branches
+- SSH client mode selection
+
+## [2.0.0] - 2025-01-09
+
+### Changed
+- **BREAKING**: Removed per-submodule Skip LFS configuration
+- Skip LFS now applies to the entire repository including all submodules
+- Significantly simplified code by removing complex LFS override logic
+
+### Fixed
+- Submodule LFS inheritance issues
+- Debug message accuracy
+
+## [1.5.0] - 2025-01-09
+
+### Added
+- SSH key support for individual submodules during update
+- Submodules can now use different SSH keys as configured
+- Improved error handling for SSH submodule authentication
+
+### Changed
+- Merged "Submodule SSH Keys" into "Submodule Config" for cleaner JSON format
+
+## [1.4.0] - 2025-01-09
+
+### Added
+- "Skip LFS" configuration option for repositories
+- "Submodule Config" section with per-submodule LFS control
+- LFS pulls can now be skipped on a per-repository or per-submodule basis
+
+## [1.3.0] - 2025-01-08
+
+### Added
+- Support for PuTTY/plink SSH client
+- -SshClient parameter to choose between OpenSSH and PuTTY
+- Automatic detection of key format (OpenSSH vs PuTTY)
+- Integration with Pageant for PuTTY keys
+
+## [1.2.0] - 2025-01-08
+
+### Added
+- Support for repository paths with spaces
+- Proper quoting for all path operations
+
+### Fixed
+- Clone operations failing when repository path contains spaces
+- Git commands not properly handling quoted paths
+
+## [1.1.0] - 2025-01-08
+
+### Added
+- Git LFS support with automatic detection
+- Submodule SSH key configuration
+- Dry run mode (-DryRun parameter)
+- Debug logging (-EnableDebugLog parameter)
+
+### Changed
+- Improved error handling and user feedback
+- Enhanced logging system with multiple levels
+
+## [1.0.0] - 2025-01-07
+
+### Added
+- Initial release
+- Multiple repository management from JSON configuration
+- Tag-based checkout
+- SSH key support for repositories
+- Automatic repository reset
+- Submodule initialization and update
+- Comprehensive error handling
+- Summary report generation

LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2025, LS Instruments AG
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.